Sometimes I'm just grateful for others to find out about those tricky details.
This excellent post http://www.eventlogblog.com/blog/2007/11/setting-service-permissions-wi.html describes how to use subinacl.exe to give a user permissions to start and stop services. I've seen the method using security templates and find the subinacl.exe version much easier for a quick & dirty fix.
Thanks Ingmar!
Here an example of a script:
--------------------------------------------------------------------------------------------------------------------------
rem Frank Grossmann 2007
rem give user right to start and stop certain services
rem download windows resource kit tools first (or single download subinacl.exe)
rem do a sc \\machine query > servicelist.txt first to get service names of a machine
SET WHICHUSER=DOMAIN\USERNAME
c:
cd "\program files\windows resource kits\tools"
subinacl /service OracleDBConsoleinteg /GRANT=%WHICHUSER%=TO
subinacl /service OracleOraDb10g_home1iSQL*Plus /GRANT=%WHICHUSER%=TO
subinacl /service OracleOraDb10g_home1TNSListener /GRANT=%WHICHUSER%=TO
subinacl /service OracleServiceINTEG /GRANT=%WHICHUSER%=TO
cd\
A site was upgraded from WSS 2 to WSS 3 / Sharepoint 2007.
We've had some minor issues with this site - until we found one issue we couldn't solve: InfoPath Forms could not be published as web forms to this site.
We found out that other sites on the same server which were not upgraded previously did not have this issue.
Well, let's create a new sharepoint installation from scratch and then do a content deployment job to see if this will solve the issue.
1st of all the content deployment job would only import objects in the new site if I set "Security information in the content deployment" to None. I'm not sure if I'm supposed to setup the Users on the new site first or how this is supposed to be working.
The job log looked terrible, here some excerpts:
11/14/2007 3:18 AM The setup path is from Windows SharePoint Services version 2.0 and was not upgraded to version 3.0 Lists/AnfragenAngebote/AllItems.aspx
11/14/2007 3:18 AM The setup path is from Windows SharePoint Services version 2.0 and was not upgraded to version 3.0 Lists/AnfragenAngebote/DispForm.aspx
11/14/2007 3:18 AM The setup path is from Windows SharePoint Services version 2.0 and was not upgraded to version 3.0 Lists/AnfragenAngebote/EditForm.aspx
11/14/2007 3:18 AM The setup path is from Windows SharePoint Services version 2.0 and was not upgraded to version 3.0 Lists/AnfragenAngebote/NewForm.aspx
These 4 forms were not exported for all those lists that were created long time ago using WSS 2.0.
However, the jobs succeeded and imported most items successfully into the new site.
In the new site (which looked fine otherwise, except for the missing information on item creators), when trying to add a new item to a list, the error appears "Invalid Page URL:" and nothing happens.
When trying to edit an item the page would reload on the start page of the site.
First I've tried SharePoint designer to copy another NewForm.aspx from another list, but that would actually reference items specific to that list in the ListFormWebPart. I haven't succeeded in changing the values so that in the end it would work.
Next I've tried going through the different SQL tables to see if I could solve this issue by tweaking the list settings in dbo.AllLists, it seems that the WebPart from dbo.WebParts was missing anyway.
Even MS doesn't offer a solution to this issue, instead the KB article http://support.microsoft.com/kb/935504/en-us suggests to recreate the list from scratch. Nice.
You know what worked in the end: Use Sharepoint Designer 2007, open up both sites in two windows, drag and drop the missing forms (AllItems.aspx, DispForm.aspx, EditForm.aspx, NewForm.aspx) into the same place on the new site.