SharePoint Server Enterprise Site Collection features activati
in [Portal Server]
|
From: Vince Rothwell on 30 Jan 2007 06:37 The issue you are having is because SharePoint is trying to subit a job for OWSTimer (SPJobDefinition). To do this it needs to update the ConfigDB, which you probably don'y have access to. My guess is that your site AppPool is using an account which cannot access the ConfigDB or that you are logged in with an account which is not a farm administrator. Your best bet is to ensure you are Farm Admin and activate the feature using stsadm -o activate feature -name <feature folder name> -url http://<your site> HTH, TheKid "AVantaram(a)gmail.com" wrote: > > Hello Jason/Lori, > I am facing the same problem with Office SharePoint Server Publishing > Infrastructure Feature (access denied). I tried what you have > suggested here (giving permissions to the user in Central Admin, > Shared Services) but the error still persists. Have you, by any > chance, fixed this prooblem and if so, can you let me know what the > remedy is. This is driving me nuts! > Thanks, > Abhi. > > On Jan 12, 10:19 am, jas...(a)gmail.com wrote: > > Im having the same issue with the Office SharePoint Server Publishing > > Infrastructure Feature. I get an access denied error message and the > > event log shows > > > > ****************************** > > Event log message was: 'Failed to provision the scheduling job > > definitions. Page scheduling will not succeed.'. Exception was: > > 'System.Security.SecurityException: Access denied. > > at Microsoft.SharePoint.Administration.SPPersistedObject.Update() > > at Microsoft.SharePoint.Administration.SPJobDefinition.Update() > > at > > Microsoft.SharePoint.Administration.SPWorkItemJobDefinition.Update() > > at. ect ect > > ***************************** > > > > I was able to enable the Publishing Infrastructure features on another > > site that was using a team site template. The site I'm having problems > > with is using a Blog template. I dont think the site template is the > > issue. > > > > I have made my self an administrator everywhere I could think of > > 1. Central Admin. > > 2. Shared Services. > > 3. the site its self. > > > > Could this have to do with the Application Pool the sites are running > > under? > > > > Please help.... > > > > Jason. > > > > Lori wrote: > > > I also receive this error when accesing excel servcies. > > > > > Excel Services: Unexpected exception while trying to access Shared Services > > > Database;. Error = ExcelServerSharedWebApplication.Local: Could not get > > > ServerContext.Current, which indicates that either SharePoint or the SSP > > > infrastructure isn't provisioned correctly or that we're running outside of > > > a web context.. > > > > > For more information, see Help and Support Center at > > >http://go.microsoft.com/fwlink/events.asp. > > > > > Please help, I don't want to uninstall everything ... > > > Lori > >
From: Wes Bowling Wes on 1 Feb 2007 17:14 Im having the same exact problem. Has anyone solved this, and what exactly did you do? "Vince Rothwell" wrote: > The issue you are having is because SharePoint is trying to subit a job for > OWSTimer (SPJobDefinition). To do this it needs to update the ConfigDB, which > you probably don'y have access to. > > My guess is that your site AppPool is using an account which cannot access > the ConfigDB or that you are logged in with an account which is not a farm > administrator. > > Your best bet is to ensure you are Farm Admin and activate the feature using > stsadm -o activate feature -name <feature folder name> -url http://<your site> > > HTH, TheKid > > > "AVantaram(a)gmail.com" wrote: > > > > > Hello Jason/Lori, > > I am facing the same problem with Office SharePoint Server Publishing > > Infrastructure Feature (access denied). I tried what you have > > suggested here (giving permissions to the user in Central Admin, > > Shared Services) but the error still persists. Have you, by any > > chance, fixed this prooblem and if so, can you let me know what the > > remedy is. This is driving me nuts! > > Thanks, > > Abhi. > > > > On Jan 12, 10:19 am, jas...(a)gmail.com wrote: > > > Im having the same issue with the Office SharePoint Server Publishing > > > Infrastructure Feature. I get an access denied error message and the > > > event log shows > > > > > > ****************************** > > > Event log message was: 'Failed to provision the scheduling job > > > definitions. Page scheduling will not succeed.'. Exception was: > > > 'System.Security.SecurityException: Access denied. > > > at Microsoft.SharePoint.Administration.SPPersistedObject.Update() > > > at Microsoft.SharePoint.Administration.SPJobDefinition.Update() > > > at > > > Microsoft.SharePoint.Administration.SPWorkItemJobDefinition.Update() > > > at. ect ect > > > ***************************** > > > > > > I was able to enable the Publishing Infrastructure features on another > > > site that was using a team site template. The site I'm having problems > > > with is using a Blog template. I dont think the site template is the > > > issue. > > > > > > I have made my self an administrator everywhere I could think of > > > 1. Central Admin. > > > 2. Shared Services. > > > 3. the site its self. > > > > > > Could this have to do with the Application Pool the sites are running > > > under? > > > > > > Please help.... > > > > > > Jason. > > > > > > Lori wrote: > > > > I also receive this error when accesing excel servcies. > > > > > > > Excel Services: Unexpected exception while trying to access Shared Services > > > > Database;. Error = ExcelServerSharedWebApplication.Local: Could not get > > > > ServerContext.Current, which indicates that either SharePoint or the SSP > > > > infrastructure isn't provisioned correctly or that we're running outside of > > > > a web context.. > > > > > > > For more information, see Help and Support Center at > > > >http://go.microsoft.com/fwlink/events.asp. > > > > > > > Please help, I don't want to uninstall everything ... > > > > Lori > > > >
From: Vince Rothwell on 2 Feb 2007 06:19 Wes, I am pretty sure this is to do with the AppPool account of your site collection. Using STSADM should work, providing you run from an account which is a Farm Administrator. You could also try... Temporaraily changing the AppPool of your web application (where you are trying to activate the feature) to be the same as the central admin AppPool user. 1. Goto IIS Admin 2. Goto the properties of the web application you are using to activate the feature, goto 'Home Directory'. 3. Change the AppPool to the Central Admin AppPool. 4. IISRESET 5. Activate your feature. 6. Change the AppPool back to the original. The error is purely because the Feature is trying to create Job Definitions for OWSTIMER within cetral Admin (Operations->Job Definitons). The AppPool account does not have permission to do this (Access to the SahrePoint_Config DB). Once these jobs have been created and the feature activated you no longer need the permission. If this doesn't work have a look at the /12/LOGS folder to see what error (if any) is being produced Let me know if it does work...it should I just tried it!! Vince -- http://blog.thekid.me.uk "Wes Bowling" wrote: > Im having the same exact problem. Has anyone solved this, and what exactly > did you do? > > > "Vince Rothwell" wrote: > > > The issue you are having is because SharePoint is trying to subit a job for > > OWSTimer (SPJobDefinition). To do this it needs to update the ConfigDB, which > > you probably don'y have access to. > > > > My guess is that your site AppPool is using an account which cannot access > > the ConfigDB or that you are logged in with an account which is not a farm > > administrator. > > > > Your best bet is to ensure you are Farm Admin and activate the feature using > > stsadm -o activate feature -name <feature folder name> -url http://<your site> > > > > HTH, TheKid > >
From: Wes Bowling on 2 Feb 2007 13:59 That worked!!!! Thank you "Vince Rothwell" wrote: > Wes, > > I am pretty sure this is to do with the AppPool account of your site > collection. > > Using STSADM should work, providing you run from an account which is a Farm > Administrator. > > You could also try... > > Temporaraily changing the AppPool of your web application (where you are > trying to activate the feature) to be the same as the central admin AppPool > user. > > 1. Goto IIS Admin > 2. Goto the properties of the web application you are using to activate the > feature, goto 'Home Directory'. > 3. Change the AppPool to the Central Admin AppPool. > 4. IISRESET > 5. Activate your feature. > 6. Change the AppPool back to the original. > > The error is purely because the Feature is trying to create Job Definitions > for OWSTIMER within cetral Admin (Operations->Job Definitons). The AppPool > account does not have permission to do this (Access to the SahrePoint_Config > DB). > > Once these jobs have been created and the feature activated you no longer > need the permission. > > If this doesn't work have a look at the /12/LOGS folder to see what error > (if any) is being produced > > Let me know if it does work...it should I just tried it!! > > Vince > > -- > http://blog.thekid.me.uk > > > "Wes Bowling" wrote: > > > Im having the same exact problem. Has anyone solved this, and what exactly > > did you do? > > > > > > "Vince Rothwell" wrote: > > > > > The issue you are having is because SharePoint is trying to subit a job for > > > OWSTimer (SPJobDefinition). To do this it needs to update the ConfigDB, which > > > you probably don'y have access to. > > > > > > My guess is that your site AppPool is using an account which cannot access > > > the ConfigDB or that you are logged in with an account which is not a farm > > > administrator. > > > > > > Your best bet is to ensure you are Farm Admin and activate the feature using > > > stsadm -o activate feature -name <feature folder name> -url http://<your site> > > > > > > HTH, TheKid > > > >
|
Pages: 1 Prev: Can't uninstall MOSS 2007 Next: Failed setup configuration on SharePoint 2007 |