I am unable to publish website in visual studio 2010.. My server have changing some where.. so i can't connect with exact domain name. They gave me one IP address. But If i put IP Address instead of Target Location in publish method, it is showing an error as following,
It is not valid disk path or URL. Invalid URI: The format of the URI could not be determined.
Please help me what will do?
Related
I have two Windows 10 machines. One I can start up a debug session by selecting of typing F5 and the other gives me a message that I cannot connect to IIS Express.
Starting up the debugger on the machine that doesn't work shows:
Starting IIS Express ...
Successfully registered URL "https://localhost:44342/" for site "BSoftSolutions" application "/"
Registration completed for site "BSoftSolutions"
IIS Express is running.
Failed to register URL "http://localhost:51136/" for site "BSoftSolutions" application "/". Error description: The process cannot access the file because it is being used by another process. (0x80070020)
I have been unable to find the differences in these two machines that would cause Visual Studio to fail to connect to IIS?
I install jexus and ran a project diagnostic which gave me this report
IMPORTANT: This report might contain confidential information. Mask such before sharing to others.
-----
Scan the folder C:\Users\RKevi\Source\Repos\BSoftSolution\BSoftSolutions for project files.
1 project(s) are detected.
* BSoftSolutions.csproj
Project file: C:\Users\RKevi\Source\Repos\BSoftSolution\BSoftSolutions\BSoftSolutions.csproj.
IIS Express configuration file: C:\Users\RKevi\source\repos\BSoftSolution\.vs\BSoftSolutions\config\applicationHost.config.
Analyze ASP.NET Core project.
Visual Studio launchSettings.json: C:\Users\RKevi\Source\Repos\BSoftSolution\BSoftSolutions\Properties\launchSettings.json.
Extract debugging profiles.
Found 2 profile(s).
* IIS Express
* BSoftSolutions
Extract IIS settings.
sslPort is 44342.
applicationUrl is http://localhost:51136.
Binding localhost on *:51136 (http).
Binding localhost on *:44342 (https).
A matching binding is found for https://localhost:44342/.
I have an error where everytime I open Visual Studio, I get the following error:
TF205020: Could not connect to server ‘tfs.server.com\collectionname’. This server was used in your last session, but it might be offline or unreachable. Confirm that the server is available on the network. To attempt to connect again, or to a different server, click ‘Connect To Team Foundation Server’ in Team Explorer or the Team menu.
The server returned the following error: TF400324: Team Foundation services are not available from server tfs.server.com\collectionname.
Technical information (for administrator):
The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.We were unable to automatically populate your Visual Studio Online accounts.
This is an on-premise TFS 2013 Update 4.
I always get this error when starting Visual Studio and I have to go into Team Explorer and explicitly connect to the server to get it to connect correctly.
The issue is that the URL in the error above is wrong. It is missing a virtual directory.
Correct URL: https://tfs.server.com/tfs/collectionname
Url in Error: https://tfs.server.com/collectionname
As you can see the tfs directory is missing. I can see that the server is setup correctly in Team Explorer and I can also see that it is setup incorrectly in the Workspace configuration. Here is a picture of the workspace config.
My question is:
Where does this URL come from and why is it different to that stored in Team Explorer?
The URL is stored in your sln file. You can either do File -> Source Control -> Advanced -> Change Source Control
Or you could crack open the sln file in notepad and change it there.
I would recommend brute force approach first. Delete that workspace and create new one from scratch.
We have reinstalled ProGet as we rebuilt our server after a security hole was discovered (unrelated to ProGet). The feed is visible in the browser, but inaccessible in Visual Studio.
While rebuilding our server, we have ProGet running on a temporary Azure server, which is working and serving our NuGet packages. In comparing the two, one notable difference is the API endpoint URL for the feed. For the ProGet on Azure, it is a reasonable looking, fully qualified URL.
On the ProGet we're attempting to set up while building our new server, it actually contains a password and the word "Default" (we have deprecated this password).
This doesn't seem to be right, but I don't think it can be changed. I've tried reinstalling ProGet, but it's retaining my packages and the feed.
How can I fix this so ProGet will serve Visual Studio? Thanks in advance.
What version of ProGet are you using?
If it's v3.7 or later, the "Package Source URL" on the Feed Overview page is what you want to enter into Visual Studio:
The "Default" you're seeing is simply the feed name, and there are no passwords visible in that URL. The host name displayed there is simply the name of the machine it's running on, so you can also use a DNS name or IP address if you're on Azure (i.e. http://{sitename}.cloudapp.net/nuget/{feedname})
This was corrected by clearing the value in the ODataBaseUrl in Advanced Settings. Upon doing this, the API Endpoint URL changed to what it should be- a fully qualified URL rather than a strange string.
I've created a web service in Visual Studios fully functional as I've been able to test it through localhost. I've attempted to publish it from visual studios following a few random guides but each time I try it I keep getting errors.
This is my most recent error.
Error 3 Web deployment task failed. (The specified credentials cannot be used with the authentication scheme 'Basic'.)
The specified credentials cannot be used with the authentication scheme 'Basic'.
Default credentials cannot be supplied for the Basic authentication scheme.
Parameter name: authType 0 0 RacoCS
My previous error was in reference to the URL I would try to publish it.
Which publication method are you trying to use. Visual Studio let you publish your web apps in various ways. The less likely to have problems is to file system and then manually create a web site in IIS pointing to the directory where the publication files are. Good luck
I'm making a Sharepoint visual web part in Visual Studio 2010 and it seems like out of nowhere I started receiving the error: "Error occurred in deployment step 'Recycle IIS Application Pool': Not found"
In the output for my program it says which application pool it's looking for and I know it exists because it shows up in IIS Manager
Now I've already tried resetting IIS, along with recycling the application pool manually in IIS Manager.
Really I'm sort of at the end of my rope and any help would be greatly appreciated.
This usually happens when the user that has run Visual Studio doesn't have rights to Recycle the IIS application pool.
To solve this, run visual studio with some user who has rights (shift + right button -> run as different user) or try to follow this:
http://msdn.microsoft.com/en-us/library/aa954062%28v=bts.70%29.aspx
The simple solution for the above issue is
Step1:Close the Visual Studio
Step2:ResetIIS
Step3:Open Run and Enter Services.msc, Restart the "Windows Management Instrumentation" service
Step4: Recycle the Application pool in inetmgr.
Step5:Reopen the VisualStudio now deploy.
Hope it will help others.
Thanks & Regards
Kishore Appini
When I experienced the same error, checking the following helped me:
Make sure the Web Application exists on SharePoint.
Make sure the site collection you are trying to deploy to, exists.
This is the siteURL specified in your project's properties. To see
this property, you have to press the F4 key after selecting the
project in solution explorer (in Visual Studio).
In my case, I had not created the site collection and also the siteURL had a previous server mentioned in it.
You need to set the 'Site URL' correctly in the project properties.
click on your project name in the solution explorer and press F4 for properties.
Then check the Site URL.
The Site URL must be the same as Project Server URL.
example http:// spsw001/pwa
This solved the problem when I got this error message.
This must be the solution for the scenarios:
http://praveenbattula.blogspot.in/2013/07/error-occurred-in-deployment-step.html
If you have a public URL for your collection which is a DNS entry that is pointing to your SharePoint server then what you need is an "Alternate Access Mapping".
Go to Central Admin > Application Management > Configure Alternate Access Mappings and create an internal URL for your public URL.
Set your project server url property to point to the newly created alternate access mapping and it should work.
Note: This is valid for SP 2013
In my case it was due to missing database permissions. As mine was a DEV box, I just added my Windows account (=the account I was logged into the DEV server) to SQL Server as sysadmin.