SharePoint 2010 / 2013 ASP.NET 4.0

Friday, March 11, 2011

The Web application at ... could not be found. Verify that you have typed the URL correctly.

Yesterday my colleague showed me this error. He was trying to open a SPSite object using a URL and hitting the following error: 

The Web application at ... 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.

This is common, and can have several causes.

1. The obvious: The URL does not exist on the farm.  

Solution: Change the URL you are loading to the correct one.  

2. The not so obvious: the code is in a console or windows application which you are now running with an account that does not have permissions to connect to the SQL server. 

Solution: either run the application as a different user or grant the user permissions on the SQL database.

3. The last but most important: the code is in a console or windows application that is compiled with platform target x86, while your SharePoint server is x64. 

Solution: set the platform target to "Any CPU".
at 12:48 PM
Labels: , ,

19 comments:

  1. Paolo MarconiOctober 27, 2011 at 5:26 PM

    Thanks, option 3 solved my problem. Not sure why VS 2010 running on a 64 bit machine would default to x86 target platform. I guess it is another MS feature.

    ReplyDelete
  2. Nilesh MandekarOctober 27, 2011 at 11:41 PM

    Happy to Help... :)

    ReplyDelete
  3. naveenDecember 26, 2011 at 7:28 PM

    i have used u r 3rd solution it will work for when I am login with spadmin and it will not working for ordinary users.

    ReplyDelete
  4. Nilesh MandekarDecember 26, 2011 at 9:13 PM

    Hey Navin, Try following code:

    SPSecurity.RunWithElevatedPrivileges(delegate()
    {
    // Open new SPSite and SPWeb object.
    // Write ur code here.
    });

    Reference link:
    http://snahta.blogspot.com/2008/08/understanding-runwithelevatedprivileges.html

    ReplyDelete
  5. AnonymousJanuary 10, 2012 at 8:32 PM

    Many thanks you saved me 3 hours

    ReplyDelete
  6. Riedoh SalieApril 25, 2012 at 7:51 PM

    I received this error and it was an alternate access mapping issue.

    http://riedoh.blogspot.com/2012/04/web-application-at-httpxxxxxxxxx-could.html

    ReplyDelete
    Replies
    1. Nilesh MandekarApril 26, 2012 at 1:38 PM

      Thanks for highlighting this. I'll update my post accordingly.

      Delete
    2. AnonymousOctober 4, 2013 at 11:09 PM

      Thank you! That fixed my problem.

      Delete
  7. AnonymousJune 15, 2012 at 1:34 PM

    HI

    am using web application to upload a document from local folder to sharepoint portal..for this am using asp.net web application..but am getting the same error..i.e url specfied is incorrect..How to resolve it?

    Can any one please help me out

    ReplyDelete
    Replies
    1. Nilesh MandekarJune 16, 2012 at 11:06 PM

      You might be getting FileNotFoundException. You have to do some tweaks when you want to run object model in asp.net application.
      1. VS2010 -> Properties -> .NET Framework 3.5 and run as x64 or "Any CPU"
      2. Configure the application pool to run for the .NET Framework Version v2.0 and x64. Set "Enable 32-Bit Applications" to false.
      3. VS2010 -> property page -> "Use Custom Web Server" and specify there the url of your web application in IIS7

      Delete
    2. AnonymousJune 19, 2012 at 2:17 PM

      I have changed the settings as you said.. but still am getting the same error..What to do?

      Thanks in advance

      Delete
  8. Nilesh MandekarJune 24, 2012 at 7:31 PM

    Simple workaround is to create a console application. You will not face such issues in that. is it mandatory to use asp.net application?

    ReplyDelete
  9. Syed Danish AftabJuly 15, 2012 at 11:15 AM

    thanks a bunch dude you save me. option 3 solve the problem

    ReplyDelete
  10. Rahil AlamJuly 19, 2012 at 4:16 PM

    Thanks dude!! It saved my life as well... the option 3 did the thing....!!!

    ReplyDelete
  11. Mark BeijAugust 8, 2012 at 4:12 PM

    Option 2 did it for me
    Thanks!

    ReplyDelete
  12. AnonymousOctober 18, 2012 at 9:02 PM

    Thank you very much!! Option 3 worked for me:)

    ReplyDelete
  13. AnonymousNovember 23, 2012 at 3:16 PM

    So much help thank you !

    ReplyDelete
  14. AnonymousJanuary 1, 2013 at 9:32 PM

    Thank you!
    I would have never bet on the target platform...
    Worked for me :)

    ReplyDelete
  15. ThomasSeptember 11, 2013 at 6:05 PM

    Hey, thanks for the info.
    Problem for me was lack of permission on the SQL side.
    the service account i was using to run a scheduled task to run a script didn't have enough rights

    ReplyDelete

Subscribe to: Post Comments (Atom)