thekid.me.uk

Just what I was looking for - and thanks for the link to the Microsoft Guidelines for MOSS accounts!

Thank you for this information. It was exactly what I was looking for. This really does appear to be a Bug in the way it works and I am surprised that the original post was from Feb. 2007 (over a year agao). MS has put out a service pack and the issue still exists. You would have thought they would have fixed this one too. Once again, thank you,

Bloddy Sharepoint! Thanks lots.

Great, worked for me, thanks. Brea, CA

Unfortunately, this still does not work for me. I checked the server hosting the central adminstration and the front end server. I also tried all possible accounts. It still does not work for me. I checked the log. Here's what the log says: "Feature Activation: Threw an exception, attempting to roll back. Feature 'PublishingResources' (ID: 'aebc918d-b20f-4a11-a1db-9ed84d79c87e'). Exception: Microsoft.SharePoint.SPException: Provisioning did not succeed. Details: Failed to provision the scheduling job definitions. Page scheduling will not succeed. OriginalException: Access denied. ---> System.Security.SecurityException: Access denied. at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPJobDefinition.Update() at Microsoft.SharePoint.Administration.SPWorkItemJobDefinition.Update() at Microsoft.SharePoint.Publishing.Internal.RootProvisioner.<>c__DisplayClass5.<AddSchedulingJobDefinitions>b__4() at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(... " Any idea on what's going on? Thanks a bunch! Stanley

Unfortunately, this still does not work for me. I checked the server hosting the central adminstration and the front end server. I also tried all possible accounts. It still does not work for me. I checked the log. Here's what the log says: "Feature Activation: Threw an exception, attempting to roll back. Feature 'PublishingResources' (ID: 'aebc918d-b20f-4a11-a1db-9ed84d79c87e'). Exception: Microsoft.SharePoint.SPException: Provisioning did not succeed. Details: Failed to provision the scheduling job definitions. Page scheduling will not succeed. OriginalException: Access denied. ---> System.Security.SecurityException: Access denied. at Microsoft.SharePoint.Administration.SPPersistedObject.Update() at Microsoft.SharePoint.Administration.SPJobDefinition.Update() at Microsoft.SharePoint.Administration.SPWorkItemJobDefinition.Update() at Microsoft.SharePoint.Publishing.Internal.RootProvisioner.<>c__DisplayClass5.<AddSchedulingJobDefinitions>b__4() at Microsoft.SharePoint.SPSecurity.CodeToRunElevatedWrapper(... " Any idea on what's going on? Thanks a bunch! Stanley

Thanks This was very helpful to me thanks allot....

It worked but I misread your instructions and changed the sharepoint 80 application pool identity to be the same as the Central Admin application pool identity. Now it seems permantly hosed up, even after changing it back - restarting IIS a couple of times, and rebooting the server twice! I will reinstall MOSS and just do what you suggested

Also you can accomplish the same thing by going into Computer Management\Groups\ and add the account you are using for your site application pool into WSS_ADMIN_WPG. After you do that resest IIS and you should be good to go. That way the change is permanent and you don't have to worry about this again.

CDssxo

It is far easier to simply activate the feature via stsadm C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> stsadm -o activatefeature -name PublishingResources -url http://website That worked for me, anyway.

Thanks. Worked for me!

Well thanks "Rich" i tried the Applicatio pool change way , but it didnt worked well for me. Istead my site started througing error of unauthorized access from IIS process. It was glitching but after running the stsadm -o activatefeature -name PublishingResources -url http://website command it worked well. Even thou after running the command i have to active the publishing infrastructure feature from site collection features myself but atleast the "access denied" error was gone and things started to workout for me.

I am facing a problem during Activating "Office SharePoint Server Publishing Infrastructure" feature in a Basic Meeting site. I m getting Error : "Folders are not allowed for this list template.". But it works well for Team sites. If u have solution, please send me on my email id "goyal_arpit@yahoo.com". ThanX in Advance.

many thanks for your excellent article peace

Hi, tks to you now my MOSS is working! regards!

Got good help from here :)

Thanks a lot

This was helpful, Thanks

It is such a nice help to me Thanks

Hi I am facing a problem during Activating "Office SharePoint Server Publishing Infrastructure" feature in a Meeting site. I m getting Error : "Folders are not allowed for this list template.". But it works well for Team sites. If u have solution, please send me on my email id "shaileshraj2005@yahoo.com". ThanX in Advance.

You're beautiful. Thanks

Very helpful worked like a charm. Thanks!!

In my case it also solved the following problem : The trial period for this product has expired. at Microsoft.SharePoint.Publishing.CmsSecurityUtilities.EnsureEvaluationNotExpired() Thanks a million

Thanks a million!!! worked a treat!!!

Thanks for this - very helpful!!!

Great help! Thanks!

Perfect! Thanks.

Gracias Funciona

Hi, This also provided me with more hair on my head. Spot on the mark! Thanks, Daniel Brown

Thanks!!! Gracias !!!

Hi, I am getting an "Value does not fall within the expected range." WHEN TRYING TO ACTIVATE Office SharePoint Server Publishing Infrastructure

Thanks !!!! Hvala!!!!

Great!... I love you!!!

Muchas Gracias, me haz salvado la vida... Thanks a lot!!!!!!!!

Good Job!

Thank you for this information. This was helpful. Perfect.

Thanks for the post...It worked for me

Thanks for the stsadm command! Finally the message made clear that the feature depends on another feature with the name "PublishingPrerequisites" being activated. Now all is good. Peace and Blessings, Irene

Awesome post. I tried the stsadm command from Rich, C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> stsadm -o activatefeature -name PublishingResources -url http://website worked fine, then I activated using the GUI and kaching, we're in the money!

Spank you very much. This was most helpful.

Thanx for the information. It was of utmost help.

* FIXED * Just run the stsadm command that Rich suggests above...works fine (you'll still need to go into site administration - site features and manually enable it after you run the command however). No sense mucking up your sites by changing app pools back and forth..bad idea for a production site! SharePoint is tempermental enough already.

Fixed for me too. Before paying with IIS I used STSADM as Rich, and now the Activate Feature button in my Site Collection Features is working. Bloody Sharepoint ! C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> stsadm -o activatefeature -name PublishingResources -url http://website

worked for me!!! Thanks Vincent

Saved my day. Thank you.

Hello: I am receiving "Folders are not allowed for this list template" when i try to enable publishing on the site collection...I have tried using the cmd line (stsadm) also but to no avail. Can anyone help?? Mail me at support@allaboutpak.com

Great Article ..... Thanks buddy

It was really useful for me ... Thanks lot ..........

very useful....

i am getting an access denied message. This is a brand new installation of SBS 2008 and MOSS 2007 where i am the only user, any ideas why i get an access denied message when using the stsdam command?

Solution is smart, keepup the good works...Thank you.

This work well for me. Thanks a lot.

Awesome! Thanks so much! Leave it to SharePoint developers! So damn convoluted.

BINGO! Thanks for the post - this was exactly the solution I needed!

thanks alot, it's work with me very well but i want to know what is happend about this process or what is the idea to change the apppool to admin then back it again?? many thanks.

stsadm worked . Thanks a lot for this information.

Hi, Our WSS Team site was migrated to MOSS2007.& bymistake I activated "Office SharePoint Server Publishing Infrastructure" feature & now i am trying to deactivate it but it is giving error.My big problem is that after that activation it created many changes I want to remove those.But how can i do it.Plz suggest me any solution. Thanks

If anyone have solution, please send me on my email id "jeenim.dhumal5@gmail.com". Thanks in advance...

Hi, Our WSS Team site was migrated to MOSS2007.& avoiding error of creating site from template bymistake I activated "Office SharePoint Server Publishing Infrastructure" feature & now i am trying to deactivate it but it is giving error.My big problem is that after that activation it created many changes I want to remove those.But how can i do it.Plz suggest me any solution. If anyone have solution, please send me on my email id "jeenim.dhumal5@gmail.com". Thanks in advance...

Thanks a lot.. it is really helpful block ...

This worked GREAT! Thanks! I later found a more universal fix...Just add the account you use for administering SharePoint to the following Groups in Computer Management: (1) WSS_ADMIN_WPG (2) WSS_WPG

Consider whenever changing the application pool accounts to go through central admin and use the Service Accounts section instead of IIS. Especially in a farm where it will create the timer job to be processed by all servers. Evaluate properly before deciding to add accounts intoe WSS_ADMIN_WPG and you are providing the account more access than necessary on the server. If you are looking for some elevation of permissions for application pool account, avoid adding it to WSS_ADMIN_WPG, or the farm Admin account. Rather try giving it permissions for its web application through policy for web application in central administration.

Thank you for this information. It is exactly what I am looking for.

Adding the App Pool user to the WSS_ADMIN_WPG and WSS_WPG groups did not work for me and I wonder why not? Anyone?

I got a different problem. But the solution is the same. http://dotnetdreamer.com/2009/04/27/access-denied-activating-microsoft-office-server-publishing-infrastructure/

Hi Rothwell thanks for the post. It helped me lot and saved my time..

Greate information. Thanks.

I have an issue: when I activate Office SharePoint Server Publishing Infrastructure feature (using the GUI) we are loosing the capability to have the new created sites on the top tool bar. Can someone help me? If yes please send me an email at: gburcus@hotmail.com

Pelo2Y bugagaga348934850934859038.txt:10:20

1sjbbz it�s nice post, specially newbie like me,

Thanks : Work for me: :D >It is far easier to simply activate the feature via stsadm >C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> stsadm -o activatefeature -name PublishingResources -url http://website >That worked for me, anyway.

BijcmU nice job, very thanks�,

C1mZP8 Don�t you think he is a little late for the game?,

Great work �. Thanks for your ideas.,

R6YVyd it�s nice post, specially newbie like me,

it�s nice post, specially newbie like me,

Thanks I�ll give that a go!,

thanks for the command! it worked great solved the issue

Thanks I�ll give that a go!,

Good Thank you It�s very beautifully,

Thanks I�ll give that a go!,

Oh hell yeah� no graphical smilies around here.,

tr2.txt;20;50

A very good article. Thanks.

Also you can activate the feature via stsadm......... C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> stsadm -o activatefeature -name PublishingResources -url http://website This is working for me....

thanks this was really help full.

Perfect, thank you.

Thanks a lot. This is a good trick.

Thanks ! This worked !

C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BIN> stsadm -o activatefeature -name PublishingResources -url http://website did not work Failed to find the xml file location feature.xml'

This works for me greate, Siva Charan Gavvala

Worked for me, thank you so much!!!!!!!

http://blogs.msdn.com/sharepoint/archive/2009/06/25/service-pack-2-update.aspx

I got the same problem but the solution is different. http://blogs.msdn.com/sharepoint/archive/2009/06/25/service-pack-2-update.aspx

Thanks.. It worked!!