Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
Generate Activation Context failed for <file name>. Reference error message: <error message>
|English: This information is only available to subscribers. An example of English, please!|
|Concepts to understand:|
What is an activation context?
What is the role of Side-by-Side?
File: C:\Program Files\Citrix\Server Resource Management\Memory Optimization Management\Data\ALT1EE.tmp - This problem was fixed by reinstalling the 2008 Visual C++ redistributable from Microsoft (9.0 version).
In my case, we are running SQL Server 2005 on a server with Windows Server 2003 SE R2 SP2. We received several instances of the "Side by Side" errors stating the following:
"Generate Activation Context failed for C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\msmdctr90.DLL."
"Resolve Partial Assembly failed for Microsoft.VC80.CRT.mui. Reference error message: Access is denied."
Just like Max stated, to resolve this issue I had to give the "Performance Log Users" List Folder Contents permissions, which is on the Security tab of either of the following folder locations:
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn
c:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin
This resolved my issue.
See also EV100260 (Event Log Error - Resolve Partial Assembly failed for Microsoft.VC80.CRT.mui).
- Error message: "The manifest file contains one or more syntax errors" - In my case, we have UltraBac 8.2 installed on our Windows 2003 Standard 64-bit edition server. The error description referenced the file “C:\Program Files\UltraBac8\x64\MFC80U.DLL”. Installing the Microsoft Visual C++ 2005 SP1 Redistributable Package solved the error.
Error message: "The operation completed successfully" - In my case, I got this error while starting MSN Messenger. Deleting the %windir%\WinSxS\Policies folder fixed the problem for me.
Error message: "The referenced assembly is not installed on your system." - This problem can occur when you have version 5.2.3790.2426 or a more recent version of the Winlogon.exe program installed. See ME914061 for a hotfix applicable to Microsoft Windows Server 2003.
Error message: "The referenced assembly is not installed on your system." - This may occur if This problem occurs because the run-time libraries are not installed on the Microsoft Dynamics CRM server. See ME923014.
Error message: "The system cannot find the file specified." - This problem occurs because SQL Server 2005 requires the GetSystemTimes function. The GetSystemTimes function is included in Windows XP Service Pack 1 (SP1) and in later Windows XP service packs. See ME922669.
Error message: "The operation completed successfully." combined with "The referenced assembly is not installed on your system." - This problem occurs if the following packages are not installed locally on the SoftGrid Client: .Net Framework 2.0 or Microsoft Visual C++ Redistributable Package. See ME939084.
See also MSW2KDB for additional information about this event.
I received 2 of these errors on Windows XP SP2 with the following descriptions: "Generate Activation Context failed for C:\WINDOWS\WinSxS\x86_Microsoft.VC80.MFC_1fc8b3b9a1e18e3b_8.0.50727.42_x-ww_dec6ddd2\MFC80.DLL. Reference error message: The operation completed successfully" and "Resolve Partial Assembly failed for Microsoft.VC80.MFCLOC. Reference error message: The referenced assembly is not installed on your system". To resolve this problem, I used the Microsoft Visual C++ 2005 Redistributable Package to install the runtime libraries (ME923014). The root cause, which was identified later on, was Logitech's QuickCam software V10. I uninstalled it and installed QuickCam Software V11 which did not require the Microsoft Visual C++ Libraries patch as well. Hope this helps.
See the link to "Diagnosing SideBySide failures" - EV100040 - for an useful blog on how to debug this error in Vista.
One additional note regarding Max Ustinov's comment:
If you have multiple instances of SQL Server, you will need to repeat this process for each instance. For example, I have a default instance and a named instance. I must add the appropriate permissions to the bin folder of each instance. The folder for the default instance is the same one Max showed us:
C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin.
The folder for the named instance is:
C:\Program Files\Microsoft SQL Server\MSSQL.4\OLAP\bin.
The folder requiring the permissions will be shown in the event regarding "msmdctr90.DLL".
I had 2 instances of this event in a row on a SQL 2005 Server. The first error stated "Resolve Partial Assembly failed for Microsoft.VC80.CRT.mui. Reference error message: Access is denied". The second error immediately after said "Generate Activation Context failed for C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\msmdctr90.DLL. Reference error message: Access is denied". These errors may also be accompanied by event 1008 and 1023 from source Perflib.
I found that these errors are caused by the "Performance Logs and Alerts" service if it runs as "Network Service”, which is a member of "Performance Log Users" local user group. Although the individual DLL permissions are set, this group does not have enough permission to SQL AS bin folder. To fix this problem, for the "Performance Log Users" local user group, modify or add "List Folder Contents" permissions in the following folder:
C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin.
This event occurs in conjunction with EventID 32 from source SideBySide and it is caused by an application that was not packaged with all of the necessary runtime files. In my case this was caused by the Logitech SetPoint software and was solved by getting the appropriate C++ 2005 Redistributable Package.
When you start the Date and Time tool in Control Panel in Microsoft Windows Server 2003 64-Bit Edition, the Date and Time Properties dialog box may not display the date and time correctly. See ME841082 for a hotfix applicable to Windows Server 2003 64-Bit Edition.
|Private comment: Subscribers only. See example of private comment|
|Links: Microsoft Visual C++ 2005 Redistributable Package, EventID 32 from source SideBySide|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (1) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated