    
|
 | | |
Front-end file system cache problems might occur after a SharePoint configuration database restore.March 25, 2010 17:41
For some of the Infopath forms we received an error while upgrading the form to a newer version. The error statement told us that we could not update the form because of an object in the database with the same ID. To resolve the error we tried to remove the existing form, but instead of removing the form, SharePoint decided to do the opposite and it tried to start some kind of upgrade process. We had no more options to upgrade or even delete the existing form. Tags: Cache, Configuration database, deployment, Infopath, KB, WSP.Visual Studio and SharePoint 2010 new SPSite returns FileNotFoundExceptionMarch 22, 2010 13:26While writing my first console application to communicate with SharePoint 2010, I was surprised to receive a FileNotFoundException during the creation of a new SPSite. The line SPWeb web = new SPSite(”http://localhost/”).OpenWeb();
returned the error statement: FileNotFoundException was unhandled:
The Web application at http://localhost/ 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.
At first I assumed that the error was caused by invalid user rights, but after some searching this forum post at Microsoft Technet came up with the right solution. By default the console project is build for the .Net 4 framework and and the x86 platform. Because SharePoint is only available as a 64bit version, the console app should also be compiled for the 64bit platform.
By changing the framework to .Net 3.5 and the target platform to x64 the issue was resolved. Tags: .Net 3.5, 2010, 64 bit, console, exception, File Not Found, framework, platform, spsite, spweb. |
 |
|
Last week I was working at a client who just restored one of their SharePoint environments because of a site error. Everything was functioning like normal, until we discovered a major issue with the InfoPath forms publishing mechanism.
