I've signed up for a test account on Windows Azure to test it out. I build a Hello world ASP.NET web application + database just for testing.
I installed Visual Studio 2012 RC and installed the Windows Azure software.
In Windows Azure I've created a new Website e+ Database, I think that is running fine (http://azuretest.azurewebsites.net)
I downloaded the Publish profile from Windows Azure and import it in Visual Studio. When I publish the website I select to publish the database, select the right connection string (from the publish profile).
After publishing I get this error:
Error 1 Web deployment task failed. (Could not complete an operation
with the specified provider ("dbSqlPackage") when connecting using the
Web Management Service. This can occur if the server administrator has
not authorized the user for this operation. dbSqlPackage
http://go.microsoft.com/fwlink/?LinkId=178034 Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_USER_NOT_AUTHORIZED_FOR_DEPLOYMENTPROVIDER.) 0 0 azuretest
The url's in this error message links to articles from 2008 and 2010. I don't think that I can find any good info there..
The error says
This can occur if the server administrator has not authorized the user
for this operation
but I don't think I can authorize anything on a shared Windows Azure Website, can I?
I just answered this at http://social.msdn.microsoft.com/Forums/en-US/windowsazurewebsitespreview/thread/3f99e1e3-e030-47e0-9e43-f029663ca806.
Hi Marcel, I work on the Visual Studio Web team. When we released VS 2012 RC we had the hopes that we would be able to finalize the server side components of the Update Database checkbox by the time that the RC went out. Unfortunately we were not able to do that, so the Update Database checkbox in VS 2012 RC only works if you are publshing to localhost.
We are working to get the server side pieces ready but we cannot commit to a schedule yet. I've blogged about this at http://blogs.msdn.com/b/webdevtools/archive/2012/06/14/vs-publish-dialog-update-database-dialog-disabled.aspx.
Related
I am new to azure, I have hosted a asp.net core web api in Azure App services. I am able to browse the azure link. However I am getting some internal error while accessing the service.
To find out the error I want to debug the application by attaching to visual studio. But while attaching the debugger I am getting below error as shown in the image.
ERROR POPUP WHILE ATTACHING DEBUGGER
Error: "Unable to find a process called dotnet with arguments .\APICore.dll. The process may still be starting, please try again."
APICore is my Web api project.
I have verified that REMOTE Debugging is enabled.
Application is ASP.NET Core.
Visual Studio is VS 2017 community
edition.
I've had the same problem today, and this is what worked out for me:
1) Instead of attaching the debugger via Server Explorer, go to Debug > Attach to Process...
2) Set the Connection Target to your App Service url without http and with port 4022.
So, http://myappservice.azurewebsites.net would become myappservice.azurewebsites.net:4022
3) Hit the Refresh button. You will be prompted for credentials to access your App Service. Those can be found on the MSDeploy publish profile of your publish profile file:
<publishData>
<publishProfile profileName="myappservice - Web Deploy" publishMethod="MSDeploy"
publishUrl="myappservice.azurewebsites.net:443"
userName="{USERNAME}" userPWD="{PASSWORD}" ...>
<databases />
</publishProfile>
<publishProfile profileName="myappservice - FTP" publishMethod="FTP" ...>
<databases />
</publishProfile>
</publishData>
4) After the available process show up, select w3wp.exe and hit Attach
Had the exact same issue, tried several things (open in Admin mode, open outbound port 4022, 'Attach debugger', 'Attach to process') but nothing worked.
Just switched from VS 2017 Community edition to Visual Studio 2019 - Enterprise edition and now it instantly works flawless:
Published my Azure App Service in Debug configuration
Attach debugger via the Cloud Explorer
Set the breakpoints and hit them when sending requests to the API
So perhaps switching to 2019 will solve it for you as well.
There are few options that you can try out and see if that helps.
Ensure Visual Studio is opened in Administrator Mode and follow the
same steps.
Open the Outbound ports 4022 for VS 2017 on corporate firewall.
You can also go through the below links in order to Remote debug the
application
https://learn.microsoft.com/en-us/visualstudio/debugger/remote-debugging-azure?view=vs-2017#remote_debug_azure_app_service
The answer above using a regular
"Attach to Process" using creds from a publish profile downloaded from the portal worked for me.
VS2019 (community and professional, multiple azure accounts, multiple machines, physical and virtual) here, and the cloud explorer "AttachDebugger" never worked. In fact it hung vstudio at "attaching to process" and had to kill VStudio from task manager to stop it.
Strange because at other companies/projects I didn't have this problem. For years I relied on debugging azure from desktop for a variety of projects. This particular software I inherited, and I expect that something in its origination or construction (there are several ..."sub optimal"... aspects to it).
I have a web site that works as it should on our company intranet, which I am now trying to deploy on a hosted web server. Unfortunately when a user clicks Log In it crashes with:-
Server Error in '/' Application. Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.
If I go on to the remote server's desktop, log in to Management Studio with the username and password in the site's webconfig.cfg file, then I can open the aspnetdb database, and execute dbo.aspnet_CheckSchemaVersion without any error messages or access issues.
I have read numerous other postings on this error message and none of the suggestions have helped, but I am new to web site administration and may be missing something obvious.
The web site is coded in VB.NET, and compiled with Visual Studio 2012. Third party tools used are Fusion Charts and AJAX Calendar Extender. The .NET Framework version is 4.5.
The remote server runs Windows Web Server 2008 R2 with IIS version 7.
The database server is a named instance of SQL Server Express 2008 R2.
There are five users defined in the aspnet_Users table, which I added using the .NET Users applet within IIS. I can no longer use the user management tools in IIS because I had to upgrade the site's application pool to .NET 4.0 which does not support them. However I can see the users are there.
There are no Roles defined in aspnetdb.
Does anyone have any ideas what I could be missing?
Try recreating the ASP.net procedures with something like:
aspnet_regsql.exe -S DBServerName -U DBLogin -P DBPassword -A all -d DBName
Just so this question is no longer "unanswered", I will echo Aaron Bertrand's comment, which the questioner said was the correct answer:
Does your connection string specify the database? If not, then perhaps the application is trying to execute that stored procedure in the login's default database, not the aspnet database. – Aaron Bertrand Feb 17 at 14:44
Thanks very much that was it. I changed the "Initial Catalog" in the connection string to aspnetdb, now I can log in. – user3319440 Feb 17 at 16:30
I'm developing an ASP.NET Web Forms application under Visual Studio 2012. I'm using Web Deploy and Publish Web dialog for application deploy. I'm trying to deploy a database schema using the Update database feature. I entered a connection string pointing to remote SQL Server. If I click the "Test connection" button Visual Studio says test connection is succeeded.
Then I go to Preview tab and click the Preview database link.
And in the opened window I have the message
Web deployment task failed. (Could not generate deployment script.
Unable to connect to target server. Learn more at:
http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_EXECUTING_METHOD.)
Other project files are deployed normally. I'm able to connect to SQL Server using SQL Server Management Service. But why the database could not be updated? I tried to disable server firewall - with no luck.
Visual Studio Professional 2012
SQL Server 2012
Web Deploy 3.0
Update
All works fine if I use SQL Server Authentication with the sa login instead of Windows Authentication in connection string for DatabaseEntitiesRaw. But Windows Authentication works fine for SSMS, and I want to use it since I'm deploying only from computers within my company's domain. Is it true that dbDacFx doesn't work with Windows Authentication?
Deploy script runs from AUTHORITY\LOCAL SERVICE user, so you have to add this user to SQL server. Do not foget to add db_owner role for the user.
I just created my first ASP.NET Version 4 app using Visual Studio 2010 and SQL Express 2008.
I copied the files to IIS and run the default.asp. This loads the programs main menu. So far so good.
When I open the read webform and do a read of my database I get the following Error:
Server Error in '/Diary' Application.
Failed to generate a user instance of SQL Server due to failure in retrieving the user's local application data path. Please make sure the user has a local user profile on the computer. The connection will be closed.
Any idea how to fix this error?
Did you look at support articile for the very issue.
Or even this
I am trying to get a tutorial or step by step instructions on how to connect MS Project 2010 to MS Project Server 2010.
I have installed Server 2008 R2 (64 bit), Sharepoint 2010, and Project 2010 on my server and created a new site using the project 2010 template.
I am now trying to connect my stand alone Project 2010 to that site for updates and such.
I tried the File->Info->Manage accounts option and it comes up with "Could not retrieve server initialization data."
I cannot find a step by step tutorial to set it up or to trouble shoot the error message.
Any hints or good resources would be much appreciated.
make sure you use the http:///pwa as your account URL
Also, make sure you add your users under Server Settings --> Manage Users in the PWA site, you can't just add them via SITE PERMISSIONS.
You missed one important step: creating a PWA (project web application).
After you install sharepoint and project server you must build a pwa and then enter this address to project. Here is a very good and complete guide for creating and setiing up PWA:
Create a PWA site (Project Server 2010)
Deploy Project Server 2010 to a test environment