I was checking the application log on Server 2008 R2 after completing SharePoint 2007 (SP2 including October CU) installation and found out this error message: Log Name: Application Source: Windows SharePoint Services 3 Date: 11/17/2009 1:33:13 PM Event ID: 5629 Task Category: General Level: Error Keywords: Classic User: N/A Computer: SP.sabaka.local Description: Failed to load the SafeControl assembly paths for web.config. C:\inetpub\wwwroot\wss\VirtualDirectories\8081 Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Windows SharePoint Services 3" /> <EventID Qualifiers="0">5629</EventID> <Level>2</Level> <Task>1105</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2009-11-17T18:33:13.000000000Z" /> <EventRecordID>1395</EventRecordID> <Channel>Application</Channel> <Computer>SP.sabaka.local</Computer> <Security /> </System> <EventData> <Data>Failed to load the SafeControl assembly paths for web.config. C:\inetpub\wwwroot\wss\VirtualDirectories\8081</Data> </EventData> </Event> The same error message appeared on another installation using Windows 2008 on a totally different environment. The error seems to be generated after creating SSP. Although, SharePoint is functioning fine and I am able to access SSP site and search is working as expected. However, I am getting am error in the crawl log for SSP: http://sp:8081/ssp/admin/content Error in the Site Data Web Service. I did find another post for this issue, and they suggested deleting the SSP and re-creating the SSP web application. What I did is I ran the configuration wizard and disconnected from the farm and ran it again and created a new farm and I had the same issue. I have the following concerns: 1. Is this a Bug? If yes, does MS aware of it? 2. Can this error be ignored, since everything...so far.. is working properly? (expect for the error in the crawl log, which I don't know if that has any affect on the SharePoint Farm) 3. If this is an issue needs to be fixed, any ideas on how to fix it? Thanks.

Check out this blog post http://bytelab.blogspot.com/2009/01/issues-after-restoring-moss-to-previous.htmlU need to scroll down for the particular event id that u mentioned. Also it doesnt look like it can be ignored as you might face issues down the lane

I have read this Blog before, and not sure if this is related to my situation, since I still believe it is a Bug, since I am able to re-produce it every time. I will try this workaround and see if that might fix the issue. Thanks for your reply.

Well, I have done more tests and no matter what I do I got the same results: 1. Tried to create a new SSP. Again from CA site it provisions without errors, but I still got the error in the application log. 2. Create yet another SSP and same behavior. So, I still need to resolve this issue, since it might an adverse effects in the log run.... At this point, I am using my VMs to slide and dice, so I am willing to try anything. Thanks

Hi, Please enable ULS logging, reproduce the issue, check the Event Viewer and diagnostic log to get more clues. You can post the detailed error information into the forum for analyze. For more information about how to enable ULS logging, please refer to the following article: Configure diagnostic logging settings http://technet.microsoft.com/en-us/library/cc262714.aspx In addition, try to reinstall .net 3.5 SP1 patch and IIS 7.0 patch, check the effect. Hope this helps. Rock WangRock Wang MSFT

Thanks Rock for your suggestion. I have enabled ULS logging and was able to re-produce the issue. I have scanned through the logs and found the same error in ULS logs: 11/19/2009 14:39:27.07 OWSTIMER.EXE (0x0D8C) 0x02F0 Windows SharePoint Services General 5629 Critical Failed to load the SafeControl assembly paths for web.config. C:\inetpub\wwwroot\wss\VirtualDirectories\42926 11/19/2009 14:39:28.68 OWSTIMER.EXE (0x0D8C) 0x0EB0 Windows SharePoint Services Timer 5utp Verbose Scheduled timer job Variations Propagate Page Job Definition, id {70B5DE97-33B0-4BA0-B98D-ACA20A0CB25F} at 19 Nov 2009 14:40:28 -0500 (now is 19 Nov 2009 14:39:28 -0500) 11/19/2009 14:39:28.68 OWSTIMER.EXE (0x0D8C) 0x05CC Windows SharePoint Services Topology 88b9 Verbose Determining if the current user is a SharePoint Farm Administrator 11/19/2009 14:39:28.68 OWSTIMER.EXE (0x0D8C) 0x0EB0 Windows SharePoint Services Timer 5utp Verbose Scheduled timer job Variations Propagate Page Job Definition, id {60C1C63E-AF34-4D36-A052-9DCCA550B4FF} at 19 Nov 2009 14:40:28 -0500 (now is 19 Nov 2009 14:39:28 -0500) 11/19/2009 14:39:28.68 OWSTIMER.EXE (0x0D8C) 0x05CC Windows SharePoint Services Timer 8e45 Verbose Begin invoke timer job Variations Propagate Page Job Definition, id {70B5DE97-33B0-4BA0-B98D-ACA20A0CB25F}, DB {F7B8E5EA-8900-49B5-8095-A424D8C25D37} 11/19/2009 14:39:28.68 OWSTIMER.EXE (0x0D8C) 0x0674 Windows SharePoint Services Topology 88b9 Verbose Determining if the current user is a SharePoint Farm Administrator 11/19/2009 14:39:28.68 OWSTIMER.EXE (0x0D8C) 0x05CC Windows SharePoint Services Database 880l Verbose ConnectionString: 'Data Source=SISPSQL01;Initial Catalog=WSS_SSP3_Content;Integrated Security=True;Enlist=False;Connect Timeout=15' ConnectionState: Closed So the ULS log has the same error as the one in the application log. By the way I did remove .NET 3.5 SP1 and removed .Net 3.0 feature and IIS role from Server Manager, and even re-installed MOSS and that didn't help. It's hard to believe only few people reported this error. I know it is not obvious since it creates SSP without any problems (at least according to the Central Admin UI). Thanks!

Hi, Based on my research, you can try the following suggestions: 1.Delete the SSP web application. 2.Stop the search query & index services. 3.Start the search query & index services. 4.Restart IIS. 5.Recreate the SSP web app. 6.Recreate the SSP & set back to default with any associations required. 7.Check the effect. For correctly create a SSP, please refer to the following article: Configure the primary Shared Services Provider http://technet.microsoft.com/en-us/library/cc262649.aspx Hope this helps. Rock WangRock Wang MSFT

Hello Rock and Thanks for your reply, I would like to reiterate the situation. The issue happens every time and it is reproducible on Windows 2008 platform. Which tells me that this is a BUG and MS needs to address this issue. Your solution didn't work. No matter how you slice it or dice it, it simply doesn't work and again if this is a BUG doing the previous steps is like putting a band aid on the issue and not addressing the real issue. I am not sure why this was marked as an answer, since I did state in my previous reply that the solution didn't work in my case. I have opened a MS ticket and waiting for an answer. I will update the post once I hear from MS. Thanks, Yassar

Yassar, I am seeing the same error on my system with the same configuration (Server 2008 R2 with SharePoint 2007 SP2). Have you gotten any response from Microsoft? Thanks, Alan

Hello Alan, I have opened a case with Microsoft and reported this as a bug. I will contact MS and see if they have any updates. Thanks, Yassar

I'm interested in a resolution to this issue as well, as I've now seen it on a Server 2008 R2 SharePoint install (inc SP2 and Dec 09 CU).Andy

____ All, I sent an e-mail to MS Support professional who reported this issue as a "Bug" and received an e-mail last night indicating that MS is still working on the issue. I will keep following up with on this issue and update this post. Thanks, Yassar

@All Is there any kind of solution right now? I've same problem with 4 installations, W2K8 SP2 (non R2), SharePoint 2007, SP2 Okt. 2009 CU! Thanks, Joerg

Hi, I was facing the same problem : I create a dedicated Web Application for my SSP, then, try to create the SSP and I get the same event " Failed to load the SafeControl assembly paths for web.config." After re-re-re-installing, I find a solution. It's not really clean, but it works : I create again a clean Web Application dedicated to the SSP. Inside this web application, I create a blank root site collection. I create the SSP and... this time it work. It seems that the SSP creation is buggy and cannot create proper Web.Config. So creating a collection into the dedicated SSP Web app create a good Web.config and then, the created SSP work. Have you news from MS about this, which seem to be a bug ?

Thanks for the reply, I have sent an e-mail to the support tech and waiting for his reply. I will post any information once I get any communication from him. Thanks,

I got reply from the Support Engineer: "I reviewed what I had uploaded and it had been escalated to another database but the issue is still active. It looks to be slated for SP3. I do not know if there will be an SP3 for MOSS 2007 but this is the information I found regarding this issue. Best Regards, " So, I guess the issue will be addressed in future MOSS Service Pack since the product team is busy with SP 2010.