Error Message:The File Exists. (Exception from HRESULT: 0x80070050)

Question

I installed sps3.0 on windows server 2003. It's ok and i saved any data on it.  Today i updated server to AD,and then I unload AD. When i into sps web page,i miss the error message:The File Exists. (Exception from HRESULT: 0x80070050).

 

Who can resolve this error? thanks a lot!

Answer 1

I have the same exact issue... did you find a resolution to this??

Answer 2

When you say you "updated to AD" do you mean you promoted the machine to a domain controller? If that is the case I think the answer is unpleasant. This is from the WSS 2 documentation ( found at http://office.microsoft.com/en-us/winsharepointadmin/HA011608411033.aspx) but I think it still explains the issue.

 

•

I installed Windows SharePoint Services to a computer, and then made the computer a domain controller. Now when I go to SharePoint Central Administration or to a page in my SharePoint site, I see a "file not found" error, or an "access denied" error. In order for the permissions for Windows SharePoint Services to be configured correctly, Internet Information Services (IIS) and Windows SharePoint Services must be installed to the domain controller after it is promoted to domain controller. If you have already installed IIS and Windows SharePoint Services to a computer, and you now need to make that computer a domain controller, you must uninstall IIS and Windows SharePoint Services, promote the computer to domain controller, and then reinstall IIS and Windows SharePoint Services. For more information about running IIS on a domain controller, see the IIS documentation.

 

Answer 3

so if we had IIS installed and SharePoint WSS 3 installed on the server and then it was promoted to a domain controller my next steps are to uninstall both SharePoint and IIS and then reinstall them from the sound of it.  Whe I do that am I going to loose all of the data that is in the embedded SQL Server database that was in there before the promotion of the server to a domain controller??

 

Thanks,

Derek

Answer 4

 

Hey Guys,

 

I know this is a late reply, but I ran into this issue and haven't found a great solution on the web.  The one recommendation I found did solve the problem, but took some digging.  The reason I was receiving this error was we switched domain controllers.  This gave the file exists exception.  The SID (System ID's) on the user accounts for the domain no longer matched the system ID's stored in the SharePoint UserInfo Table on the content database.

 

There are 3 things to check and one or all should solve the problem:

 

1. App pool account may need to be reset in IIS to a non domain account.  This requires a reset of IIS after changing the account to see an affect on the application

 

2. In central administration, make the user account you are trying to login as site collection administrator  (Web Applications Tab -> Select Web Application from Web Application List -> Select Site Collection Administrators -> Enter your account and click ok.  I had some sites where these two steps solved the problem.

 

3. For the other sites, I had to do some hacking on the SharePoint Database.  Please make a backup before deploying these steps in case you have issues.  I created a new site that I could access first and associated my account to that site.  This will store the correct SystemID in the userInfo table for the new site.  You can get it from that site by doing a "select tp_systemID from userinfo where tp_login = '<domain name>\<username>'"  (something to this effect).  Then you can compare that number to the system ID in the content database with which you are having trouble.  They are likely different.  If so, just update that ID in the old content database and you are good to go.  Let me know if this is helpful.  I can post the queries if need be.

 

Thanks,

Michael Brown

Affirma Consulting

http://www.affirmaconsulting.com

 

Answer 5

 Hello, I will appreciate if Michael Brown or someone else posts the needed queries in order to correctly update the userinfo tables.
Thank you in advance
Hernán Rojas.

Answer 6

I had the same problem, after recovery the SharePoint Content Database to another server in the same domain.
When the user tried to connect to the portal, he received the same message.
I solved the problem deleting a adding again the user in the website using the People and Groups option in the Site Configuration page.

Answer 7

I walked into the same problems.

I solved it by assigning two new (use users that don't exist in the current sitecollection) sitecollection administrators in the central administration.
Then I deleted al the users from the sitecollection with stsadm or a small program.

stsadm -o enumusers -url <url> will give a list of users.
You have to delete them one by one with stsadm -o deleteuser <userlogin>

OR

Create a console application.

while (web.SiteUsers.Count > offsetIndex)

    {

        if (web.SiteUsers[offsetIndex].IsSiteAdmin || web.SiteUsers[offsetIndex].ID == web.CurrentUser.ID)

        {

            offsetIndex++;

            continue;

        }

        web.SiteUsers.Remove(offsetIndex);

    }

That solved the problem for me.

Answer 8

Hi,
I will appreciate if you post the required queries as in my case Central Admin is also having the same problem.
Thanks in advance.
Saud Siddiqui