We were moving our MOSS 2007 databases from a server we are going to retire using the stsadm command line. We moved the content database with no problems. When we moved the config database, we got this error: Value cannot be null. Parameter name: str the strange thing is that after about a minute, we are able to get the site back up, but we have no admin IIS or access. We tried to re-run the configuration wizard and it bombs on step 5 and gives this error log: 04/07/2010 18:19:00 8 INF Calling SPServiceInstance.Update for instance Microsoft.Office.Server.Administration.SessionStateServiceInstance, service Microsoft.Office.Server.Administration.SessionStateService04/07/2010 18:19:00 8 ERR Task services has failed with an unknown exception 04/07/2010 18:19:00 8 ERR Exception: System.ArgumentNullException: Value cannot be null.Parameter name: str at System.Security.Permissions.FileIOPermission.HasIllegalCharacters(String[] str) at System.Security.Permissions.FileIOPermission.AddPathList(FileIOPermissionAccess access, AccessControlActions control, String[] pathListOrig, Boolean checkForDuplicates, Boolean needFullPath, Boolean copyPathList) at System.Security.Permissions.FileIOPermission..ctor(FileIOPermissionAccess access, String path) at Microsoft.SharePoint.Administration.SPFileSystemCache.GetFileInfoFromId(Guid objectId) at Microsoft.SharePoint.Administration.SPFileSystemCache.PutObjectInFileSystem(SPPersistedObject obj) at Microsoft.SharePoint.Administration.SPFileSystemCache.SetValue(Guid id, SPPersistedObject obj) at Microsoft.SharePoint.Administration.SPCache`2.set_Item(K key, V value) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.RefreshCache(Int64 currentVersionOverride, List`1& newObjects, List`1& deletedObjects, Int64& newestObjectVersion) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.RefreshCache() at Microsoft.SharePoint.Administration.SPConfigurationDatabase.StoreObject(SPPersistedObject obj, Boolean storeClassIfNecessary, Boolean ensure) at Microsoft.SharePoint.Administration.SPConfigurationDatabase.PutObject(SPPersistedObject obj, Boolean ensure) at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPServiceInstance.Update() at Microsoft.SharePoint.Administration.SPPersistedObject.Update(Boolean ensure) at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstanceInConfigDB(Boolean provisionTheServiceInstanceToo, String serviceInstanceRegistryKeyName, Object sharepointServiceObject) at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServiceInstances(Boolean provisionTheServiceInstancesToo, String serviceRegistryKeyName, Object sharepointServiceObject) at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.InstallServices(Boolean provisionTheServicesToo) at Microsoft.SharePoint.PostSetupConfiguration.ServicesTask.Run() at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()04/07/2010 18:19:00 8 INF Entering function Common.BuildExceptionMessage Also - in the event log - we are getting event 6395 insufficient permission errors - Insufficient permission to write to the configuration data cache. Value cannot be null Parameter name: str So we're stuck - any help would be appreciated.

Hi DU CJ, The error 6395 indicates there is no sufficient permissions to the configuration data cache. Please Ensure that the WSS_ADMIN_WPG and WSS_RESTRICTED_WPG local groups have been granted permissions to write to the %systemdrive%\inetpub\wwwroot\wss\config folder. See Event ID 6395 (Windows SharePoint Services health model) (http://technet.microsoft.com/en-us/library/cc561004.aspx) for more information. If your issue could not resolved, could you please let me know more information? 1. Were you in the process of database migration? 2. “we are going to retire using the stsadm command line”, what does it mean? 3. Did you follow Move all databases (Office SharePoint Server 2007) (http://technet.microsoft.com/en-us/library/cc512725.aspx)? Lambert Qin TechNet Subscriber Support in forum If you have any feedback on our support, please contact tngfb@microsoft.com Sincerely, Lambert Qin Posting is provided "AS IS" with no warranties, and confers no rights.

Hi Lambert - I tried checking and changing the permissions but just kept getting that error. And I was following that sharepoint article. What I ended up doing was taking the sharepoint config offline, then I used the wizard to create a new farm, which worked no problems, then I brought in the old content database - which all worked fine. Don't know why I couldn't fix the permissions, but everything I tried just didn't work. Thanks for the suggestions.