SharePoint Site accessibility issue with Object Model with SharePoint Installed on Windows Server 2008 R2
Hi, First of all I would explain the Installations, configurations and the server information before coming to the actual issue. Server - Windows Server 2008 R2 (64 Bit) Database Server - SQL Server 2008 (64 Bit) SharePoint Installer - Created a slip-stream installer on my own by merging (Old MOSS Installer + SP2) SharePoint App (Default Zone) - Localhost:80 OR IP1:80 (FBA, publicly Exposed) SharePoint App (Custom Zone) - Localhost:81 (Windows, only for internal use just from the server) .NET 2.0 Web App - IP2:80 (Asp.Net Web Site) Now i am going to explain the problem. I have the setup, explained above, up and running on my production server which is Windows Server 2003 with SQL Server 2005 and Sharepoint installed as MOSS without SP2. And we are on our way to upgrade to the Server 2008 R2. I have got everything ready and running without major changes to any of the application, expect one of the weird SharePoint issue. And to explain that issue, i would first explain that i have some sharepoint integration in my .NET web app where i am using the SharePoint Custom zone to handle the user management for SharePoint site with help of SharePoint Object Model. I have a code to access this custom zone using for the sharepoint user management from .net web app, which is working fine since 3 years but as we are migrating the whole thing to the above mentioned configurations, i get the some weird sharepoint issue which does not let me access this custom zone site using object model from the .net web app where i am trying to create a spsite object. I am not sure if the SharePoint installed is 32 bit or 64 bit, but i read in so many blogs people sharing some info on that. Did lot of googling on this, have come across so many solutions but nothing worked in my case.
April 7th, 2010 8:49pm

Hi, if your SharePoint is x86, you'll find your SP files within "Program Files (x86)" instead of just "Program Files". Make sure your application is compiled to "Any CPU" or your architecture. If it is the wrong one, you'll get messages like "Url not found...". Renévisit my SharePoint blog: http://www.hezser.de/blog
Free Windows Admin Tool Kit Click here and download it now
April 7th, 2010 9:11pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics