MOSS 2007 – Error enabling Office SharePoint Server Publishing Infrastructure December 1, 2008
Posted by Joel Kriel in CRM 4.0 & .Net development.Tags: moss 2007, sharepoint 2007, sharepoint server publishing feature, site collection features error, try catch, try catch consulting
add a comment
Upon trying to enable the feature for publishing in MOSS, I ran across this security error. Access denied. at Microsoft.SharePoint.Administration.SPPersistedObject.Update().
Under site settings logged in as site collection admin, go to Site Collection Administration -> Site Collection Features.
Office SharePoint Server Publishing Infrastructure
Provides centralized libraries, content types, master pages and page layouts and enables page scheduling and other publishing functionality for a site collection.
Click the Activate and this is where the error is happening.
Upon some wide searches I found this great post that provided a great work around. Here are the basic steps and link.
1. Open IIS Admin.
2. Location the Web Site for your WSS web application.
3. Goto to the properties and select the ‘Home Directory’ tab.
4. Change the AppPool to be the same as Central Administration.
5. IISRESET
6. Activate the Publishing Infrastructure feature on your site.
7. Change to AppPool back to the original.
8. IISRESET.
Activating Office SharePoint Server Publishing Infrastructure – Access Denied
Deletion Service in Microsoft CRM 4.0 June 3, 2008
Posted by Joel Kriel in CRM 4.0 & .Net development.Tags: Act!, Data Migration, Deletion Service, Microsoft CRM 4.0, try catch, try catch consulting
add a comment
When performing a bulk load using the Data Migration tool in CRM 4.0, I ran across a huge issue on how the data is backed out. I am working on a large ACT! to CRM 4.0 migration which include 73 mapping for the Contact entity and of course, it is a trial and error process. Using the Data Migration tool is perfect since you can back out the successful records until you get a clean upload. The only problem is that the deletion process sets a flag on the entity level (DeletionStatusCode = 2) rather than actually deleting the records from the database. Then the Sync service will pick up the records for deletion and physically delete them. Now the limitation to this process is that the service will only run once a day and can not be run on demand…. until yesterday afternoon. 
Welcome ScaleGroup Job Editor! Simply install on the CRM 4.0 server and now you can actually set when the delete service runs!!
Thank you to the East Region Microsoft CRM blog. I recommend checking this blog weekly for other very useful updates to all things CRM 4.0.
