Error 1 No Sharepoint Site Exists At The Specified Url
Getting "No SharePoint Site exists at the specified URL" - Visual Studio 2005 Extensions for SharePoint ★★★★★★★★★★★★★★★ MSDN ArchiveNovember 30, 20069 0 0 0 Getting the following error when I deploy my webpart by using Visual Studio 2005 extensions for SharePoint Error Message : "No SharePoint Site exists at the specified URL" In default, VS 2005 extensions using the default port 80 to deploy the webpart. If you created your webapplication/sharepoint top level website other than the default port, you will get the error message. To resolve this, In Visual Studio 2005, goto "Project ->
Office 2010 / 2007 / 2003 Microsoft SharePoint Workspace No SharePoint Site exists at the specified URL Ask a Question Sign up for Free 140 Experts currently online. Ask Questions for Free! No SharePoint Site exists at the specified URL - Microsoft SharePoint Workspace I have irritating problem. I have visual studio 2005 + WSS 3.0 extensions. i'm tring to create a web part project as follows: 1) I've created 'Web Part' solution. 2) i've changed the url in the project properties>>debug tab to the share point default site (http://il-moss-dev:6680/_layouts/MySite.aspx - is it ok?). ... Results 1 to 5 of 5 LinkBack LinkBack URL About LinkBacks Bookmark & Share Add Thread to https://blogs.msdn.microsoft.com/karthick/2006/11/30/wss-3-0-getting-no-sharepoint-site-exists-at-the-specified-url-visual-studio-2005-extensions-for-sharepoint/ del.icio.usTweet this thread Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 12-04, 09:08 AM #1 No SharePoint Site exists at the specified URL I have irritating problem. I have visual studio 2005 + WSS 3.0 extensions. i'm tring to create a web part project as follows: 1) I've created 'Web Part' solution. 2) i've changed the http://www.textndata.com/forums/no-sharepoint-site-exists-specified-804221.html url in the project properties>>debug tab to the share point default site (http://il-moss-dev:6680/_layouts/MySite.aspx - is it ok?). 3) when i'm pressing F5, there is an error: No SharePoint Site exists at the specified URL How can i solve this?? Tnx in advance, Eran Hefer. eranhef@gmail.com Reply With Quote 12-04, 02:52 PM #2 Re: No SharePoint Site exists at the specified URL I am having this same issue, and i received no help on my post about this. hopefully someone can help with this... There are walk throughs out there for the extensions, but they are all very vague and offer no troubleshooting help. I am chalking it up to being a "beta" release of the extensions. I also couldn't get it to work locally on my PC, i had to install Visual Studio on the server to get the SharePoint Solutions property tab to work. I would rather not do development work on the server, can anyone shed light on this issue as well? - Dave Dave Reply With Quote 12-04, 04:03 PM #3 Re: No SharePoint Site exists at the specified URL Are you running SharePoint on port 80? It didn't work for me until I switched it to the default IP address and port 80. Dave W wrote: Matt Reply With Quote 12-04, 04:20 PM #4 Re: No SharePoint Site exi
found VSeWSS, which greatly simplifies the deployment of web parts. But there's not much documentation on how to manage it within a complex configuration - and there are many conditions which can cause an http://mattfox77.blogspot.com/2010/05/vsewss-error-no-sharepoint-site-exists.html error on deployment - something akin to:Error 1 VSeWSS Service Error: No SharePoint Site exists at the specified URL: http:///. The Web application at http:/// could not be found. Verify that you have typed the URL correctly. If the URL should be serving existing content, the system administrator may need to add a new request URL mapping to the intended application.Log file written to: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\VSeWSS 1.3\VSeWSS1.3 service.log 0 0 This error can show error 1 up with or without the URL displayed. In either case the errors in the log show the URL attempted.Spoiler: On a single server installation, the Default Public URL must be the Server Name. If you server is named Dashboard, then your Default Public URL must be http://dashboard/Changing the Default Public URL will break VSeWSS deploymentThere are a lot of posts around the internet to try to address this issue, and in most cases, not error 1 no all situations are resolved. There are a lot of configurations that can cause this error, and so it was a configuration issue in my case. My installation consists of 64 bit versions of Windows 2008 R2 with SQL Server 2008 and Visual Studio 2008 with VSeWSS 1.3 for 64bit installed on a single VM server. SharePoint is the only site on the machine and is using the default port and URL. i did modify the setup to use the SQL Server for the config database instead of the windows internal database. App Pools are setup properly using a domain account that has full permissions both in IIS and SQL Server. The account has also been added to every group and administrator list available in SharePoint Administration, and has been added to all WPG groups in windows, but the problem persists.I then began experimenting with Alternate Access mappings, per suggestions returned by google searches on this subject. What I found was most interesting - When I added host header bindings in IIS Manager it broke the site, but when I added alternate access mappings through Central Administration those mappings worked. Several reboots and frustrating days later I returned to my site bindings, and there were the alternate access mappings I had made previously! At this point I began to get suspicious