Event Type: Error
Event Source: Office SharePoint Server
Event Category: Records Center
Event ID: 7089
Date: 16-Jan-2007
Time: 11:32:15 a.m.
User: N/A
Computer: TEST-SP
Description:
Records Center Provisioning for http://portal/records failed.
Access denied.
at Microsoft.SharePoint.Administration.SPPersistedObject.Update()
at Microsoft.SharePoint.Administration.SPService.Update()
at Microsoft.Office.RecordsManagement.InformationPolicy.PolicyResourceCollection.Add(String xmlManifest)
at Microsoft.Office.RecordsManagement.RecordsRepository.Setup.EnsureSetupExpirationActions(SPWeb web)
at Microsoft.Office.RecordsManagement.RecordsRepository.Setup.<>c__DisplayClass2.<Provision>b__0()
at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.Office.RecordsManagement.RecordsRepository.Setup.Provision(SPWeb web)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Source: Office SharePoint Server
Event Category: Records Center
Event ID: 7089
Date: 16-Jan-2007
Time: 11:32:15 a.m.
User: N/A
Computer: TEST-SP
Description:
Records Center Provisioning for http://portal/records failed.
Access denied.
at Microsoft.SharePoint.Administration.SPPersistedObject.Update()
at Microsoft.SharePoint.Administration.SPService.Update()
at Microsoft.Office.RecordsManagement.InformationPolicy.PolicyResourceCollection.Add(String xmlManifest)
at Microsoft.Office.RecordsManagement.RecordsRepository.Setup.EnsureSetupExpirationActions(SPWeb web)
at Microsoft.Office.RecordsManagement.RecordsRepository.Setup.<>c__DisplayClass2.<Provision>b__0()
at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.Office.RecordsManagement.RecordsRepository.Setup.Provision(SPWeb web)
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Creating the site comes up with an Access Denied error but is still created without shortcuts on the top link bar or quick-launch as I specify.
Found this in the SharePoint Diagnostic Logs (stored in "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\LOGS\"
The SPPersistedObject, PolicyConfigService Name=PolicyConfigService Parent=SPFarm Name=SharePoint_Config, could not be updated because the current user is not a Farm Administrator.
Tried recreating the Records Center with both my SP Farm Admin accounts with the same errors in the Windows and SharePoint logs.
My version of SharePoint Server is "Trial Version 12.0.4518.1016" and the site is using Kerberos authorization rather than NTLM
I can create Document Libraries and folders in the Records Center but cannot send files to it:
Error in IE:
An Error occurred while sending the file to the Records Repository Records Center
(Note that "Records Repository" is the name I gave the records center...)
Error on SP server:
Event Type: Error
Event Source: Windows SharePoint Services 3
Event Category: General
Event ID: 7022
Date: 16-Jan-2007
Time: 12:54:05 p.m.
User: N/A
Computer: TEST-SP
Description:
The Records Repository Records Center is not properly configured for this request.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Event Source: Windows SharePoint Services 3
Event Category: General
Event ID: 7022
Date: 16-Jan-2007
Time: 12:54:05 p.m.
User: N/A
Computer: TEST-SP
Description:
The Records Repository Records Center is not properly configured for this request.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Error in SP logs:
The Records Repository Records Center is not properly configured for this request.
Any suggestions would be appreciated, especially about the Records Center creation which I think is causing the other issues.
Nic

Error Creating Records Center
KoenP
Folks,
I managed to solve the problem I was experiencing. First, I disabled Directory Management Service (DMS) when trying to create the records site. I still tried to create it as part of a divsional site collection, and got the exact error messages folks were getting in here. Then, I took the suggestion in this thread of creating the site at the top-most level on the server, and succeeded. It is frustrating to see that we cannot add records sites below the top level, but this is a workable strategy nevertheless.
C1C Mike Byrnes
USAF Academy, CO
AlfonsAberg
Also experiencing this problem, both when Records Center is added as a separate site collection and when added to a collaboration portal as a sub-site. The error text is slightly different; instead of "access denied" it says "error in application." Text from event viewer follows:
"
Records Center Provisioning for http://scenic/cw/records failed.
Error in the application.
at Microsoft.SharePoint.SPList.UpdateDirectoryManagementService(String oldAlias, String newAlias)
at Microsoft.SharePoint.SPList.Update(Boolean bFromMigration)
at Microsoft.SharePoint.SPList.Update()
at Microsoft.Office.RecordsManagement.RecordsRepository.Setup.EnsureSetupSubmittedRecordsList(SPWeb web)
at Microsoft.Office.RecordsManagement.RecordsRepository.Setup.<>c__DisplayClass2.<Provision>b__0()
at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(Object state)
at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass4.<RunWithElevatedPrivileges>b__2()
at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElevated secureCode)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)
at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)
at Microsoft.Office.RecordsManagement.RecordsRepository.Setup.Provision(SPWeb web)
For more information, see Help and Support Center at
"
I'm wondering if this is a permissions issue with DMS...
ab2304
Anytime when i try to create a records center i get the following message
Error in the application
I have also created a new web application and created a new site collection based on the records center site definition. But it doesn't help.
Any tips!
rabi
Hello,
I am newbie . Please help me .
1)I have created a Record Center but I am not sure how I would send the documents from th document library to my record center. I dont want to do manulaly I would like to automate the process. The documents goes thru a process I defined in my workflow. When the workflow is completed I I would like the document to go to the records center.
2) how do I implement the Search
vjeyadiel
Is there any resolution to this problem.
I am experiencing this in my production enironment.
Thanks.
tssweb
http://blogs.msdn.com/recman/archive/2006/09/12/750034.aspx
In this blog one person describes this problem and he solved by NOT having the records repository under the collaboration site ...
I hope that this helps you,
Regards
Jorgen Hjartenflo
MCT
Cornerstone Sweden.
Samer Selo
To solve the problem you need to have your web application pool running under the same account as your central administrator site. To fix the temporally just go to IIS admin and do the following:
- find your sp web site under application pools
- right click on the correct application pool and select properties
- go to the identity tab and change the user credentials to the same credentials used for the central admin site.
- do an iisreset.
JIM.H.
I am also having this error.
I am a site admin so I'm not sure why I am getting this one...
Just thought I would let you know, so that you know that this is an issue still effecting people.
Thanks,
Hope you guys find a solution.
Tod.