I have a tabular model in VS that I set up per the instruction below and have successful deployed it to Power BI Premium multiple times. Yesterday I made some changes and tried to deploy but am getting an error: An error occurred while connecting to the server. When I deployed in the past it would open up the Microsoft Pick an Account window before proceeding with the deployment. That is no longer happening, which I assume is what is creating this connection issue.
I have restarted VS, restarted the server, recreated the connection configuration and changed my domain password, but all to no avail.
Anyone had this problem or have any ideas on how to get it to resume prompting me to chose my account to connect with?
Thank in advance.
Error message screenshot
https://learn.microsoft.com/en-us/analysis-services/deployment/deploy-from-visual-studio-tabular
https://learn.microsoft.com/en-us/power-bi/admin/service-premium-connect-tools#deploy-model-projects-from-visual-studio-ssdt
I figured it out. I restarted the server, then used a service account to log into the server and followed the below directions to delete my widows profile. Then when I tried to deploy it prompted me to choose which account to sign in with and deployed as expected.
https://www.isunshare.com/windows-10/tutorial-how-to-delete-user-profile-in-windows-10.html
Related
I have been deploying my Web Service via Visual Studio for over a year. Today it suddenly started giving me the error: Web deployment task failed.
Things I have noticed:
I have two other projects in the same solution that deployed to Azure without an issue.
I am able to download and change files via Cloud Explorer in VS.
I cant preview changes.
Validate Connection fails.
Things that I have tried:
Reset the publish profile via Azure, downloaded and imported it.
Selected an existing App Service.
Ensured that WEBSITE_WEBDEPLOY_USE_SCM = false before downloading the latest
publish profile.
Manually typed in the Username, Password from the Deployment Center
Hopefully someone can see something I am missing.
I was finally able to publish after a few weeks and plenty of back-and-forths with Azure support. I'm not sure if it was just time that fixed the problem, but the last thing I did before it started working was Attach a Debugger to the App Service. Hope that helps!
Over the last few days, I have had a LOT of trouble trying to get VS2013 Ultimate on my PC to connect to my TFS servers...
I will give you a quick rundown on what is happening... I did an update to VS2013 (on my PC only) to 'Update 4' a few days back and that seems to be when the problem started...
At first when I would try and 'connect to team foundation server' I was getting an error (and yeah typical end user, I didnt note what it was), I just assumed that there was a problem with that server, because we have had a few issues with it.. it wasnt until I tried to connect to a different server, that I got the same error. Thats when I realised it wasnt the server that was the problem.
I have done a bit of investigating... I can open VS2010 and connect to both servers no problems at all...
I can open VS2013 and VS2013 on my laptop (which I havent updated yet), and I can connect to both server no worries... so it is definitely NOT the TFS servers...
I found a few threads on here that all said to clear out the cache files in Team Foundation version 5.0 (and I also did 3.0 because it was there), no difference.
I went back into 'connect to team foundation server' and actually removed both of the servers from the list, in the hopes that adding them back in would fix the issue... but no... it now gives me the following error:
TS31002: Unable to connect to this Team Foundation Server: http://xxxxxxxx:8080/tfs. Team foundation server Url: http://xxxxxxxxxx:8080/tfs.
Possible reasons for this failure include:
The name, port number or protocol for the TFS is incorrect. (have checked and they are all correct)
The TFS is offline (definitely not... )
The password has expired or incorrect (I dont even get that far down the track to enter the password)
I decided that I would do a system restore, back to when I installed the update... did that, except for some reason I can only back 4 days, and the update was done prior to that..
I went into control panel and uninstalled the updates... made no difference
I ended up uninstalling VS2103 completely, restarted PC, reinstalled VS2013... went to connect to TFS... same problem...
I really have no idea at all how to fix this... can anyone at all help???
I have been using Visual Studio to deploy a Web Service to Azure; downloaded my publish profile to enable that and it was working fine for the past few weeks.
Today I tried to deploy an update and now all my deployments fail with the following:
17:25:03 - Preparing deployment for WindowsAzure1 - 25/03/2013 17:24:53 with Subscription ID 'xxx' using Service Management URL 'https://management.core.windows.net/'...
17:25:03 - Connecting...
17:25:04 - Object reference not set to an instance of an object.
17:25:04 - Deployment failed with a fatal error
I'm not sure what's failing here; is this saying it's unable to connect to the Service Management URL?
Last week I installed an SSL certificate on Azure and now I'm not seeing the option to download my publish settings. I know it used to be there but isn't now. Does having an SSL prevent me from somehow connecting to the management page?
Edit
Before leaving work I removed the certificate but when I then checked for the PublishProfile it was still not showing.
The PublishProfile is not available for any of the other users attached to the subscription - so I don't think it's related to my login.
Edit 2
A bit more drastic; I've now tried deleting my storage and service, to start from scratch. I created a new publishsettings file by removing the subscriptions already imported into Visual Studio and then following the link to "Sign in to download credentials". Next I created a new service and storage in Azure and tried to publish but the deployment still fails when connecting with
Object reference not set to an instance of an object
I have no idea what else I could try or what could be wrong, or where to look to find out.
I got the same error today. Why it wasn't working was because I hadn't uploaded the certificate in the managementportal prior to the publish.
After adding the certificate, everything worked just fine!
You can read more here: http://www.amido.co.uk/mark-omahoney/publishing-in-windows-azure-object-reference-not-set-to-an-instance-of-an-object/
The best way to solve above problem is to download the latest PublishSettings from Azure Management Portal and then use it with Visual Studio. This way your connection to Windows Azure Management Portal from local machine will be verified and validated. Once you have the basic connection working then you can publish your application to specific Windows Azure Service.
Also you can log into your Azure Management Portal and remove all old management certificates which are added in previous publishsettings download attempts.
The problem, in my case, was that my solution Cloud project had the thumbprint of the SSL certificate I'd uploaded in its ServiceDefinition.csdef and ServiceConfiguration.Cloud.cscfg. In my first edit I said that I'd removed the certificate from Azure, but hadn't then removed it from the project files; commenting them out allowed me to publish from Visual Studio again.
I'm not sure why this happened though, I had uploaded the certificate to Azure and was able to connect to my service on https in FireFox so the SSL was "working".
Web Deploy v3.6 BETA3 was released that fixes this issue. To resolve this error, you can download the Web Deploy beta and patch your VS2013 installation. http://azure.microsoft.com/blog/2014/08/11/web-deploy-3-6-beta-released/
Test Validate Connection once you installed the above Web Deploy. If it works, then fine else you can modify the proxy settings used by msbuild.exe (msbuild.exe.config) and check you can now publish from behind a proxy with Web Deploy.
Regards,
Logesh Shan
I think the certificate got corrupt. Deleting the solution .suo file and the .ccproj.user file in my Azure project did it for me.
SOLVED: Turns out the people not being able to access TFS via VS2010 were using laptops, I didn't put two and two together, and Symantec Endpoint was blocking the ports required.
Some users cannot get to the TFS 2010 server, secured by SSL, from team explorer but can via IE.
For example, I go into VS2010 SP1 and attempt to add a new server, it sits there for a while and then spits out a dialog that basically tells me "Unable to connect to the remote server". If I enter the exact same URL into IE I get access perfectly.
So
https://tfserver:8088/tfs (custom SSL port number) in IE and I get full access
The same detail entered into the add server results in
Any ideas?
Connect to tfspreview through VS2010, you need to install following things :
VS SP1: http://www.microsoft.com/download/en/details.aspx?id=23691
KB2581206: http://connect.microsoft.com/VisualStudio/Downloads/DownloadDetails.aspx?DownloadID=39070
Edit: These links are no longer available. The update is now only provided through windows update. See here
KB2662296: http://support.microsoft.com/kb/2662296
My Visual Studio 2010 issues following error when I try to map application to use local IIS:
A larger image can be viewed here:
http://img717.imageshack.us/img717/8323/errorvi.jpg
I run VS2010 as administrator and I have installed (I guess) all necessary services and IIS features.
What could be the reason?
Updated:
Having looked at the error message again, when you say you run as administrator, are you running as an account that a member of the Administrators group or the real Administrator?
If it's an account that's a member of the administrators group then you still need to right click and "Run As Administrator".
Ok. Every time when I reinstalled IIS it suddenly started to work. Then, next day issue reoccured. There was an issue with domain group policy, it turned out that some services were getting disabled with PC reset.