Software Support Forum

Hello,

Trying to create a profile and we are encountering the following error after clicking on 'Add Provisioning Profile':

 An error occurred during the processing of /prov/AddProvProfWiz.aspx. The resource object with key 'AddProvProfWiz_CreateInNewDBSection_Title' was not found

 Our product is Enterprise and is fully licenced.

Thanks in advance,

Steve

It sounds like one or more resource files is out-of-date or corrupted. You can try and update your Web Application's resource files with STSADM like so...

stsadm -o copyappbincontent

This command should update your Web Application's resource file. However, this command doesn't always work, especially when your IIS virtual directories reside outside of the INETPUB/WSS directory. If this doesn't work you can try an manually copy the file into your Web Application's directory. To do this simply copy the file..

C:\Program Files\Common Files\microsoft shared\Web Server Extensions\12\CONFIG\Resources\prov.resx

to

{Your IIS Virtual Directory}\App_GlobalResources\

Finally, your site may be looking for a local specific resource file like prov.en-US.resx. If you see a file like this in the App_GlobalResources directory please remove it. Perform an IISRESET to update your changes.

If this does not correct your issue please send a message to softwaresupport@sharepointsolutions.com and we'll arrange to have an system engineer look at your issue.

Cheers Jeremy,

that worked a treat. Chose the second option since was a little unsure as to the effects of the STSADM command would have on the whole of Sharepoint.

 Speaking of which, would the STSADM command be the way forward whenever new versions of SPA are released and need applying across all web applications?

 Thanks,

Steve

You can certainly use STSADM. However, our installation package will do all of the work. When upgrading you will be asked to 'Repair' the solution. When selected the ExCM installation package will perform all of the necessary STSADM commands. However, in some cases the STSADM -o copyappbincontent command fails to properly deploy the necessary resource files. In these cases a manual resource deployment may be required.