Event ID/Source search
Keyword searchExample: Windows cannot unload your registry file
Event ID: 32 Source: SideBySide
Dependent Assembly <assembly name> could not be found and Last Error was: <error description>
|English: This information is only available to subscribers. An example of English, please!|
|Concepts to understand:|
What is the role of Side-by-Side?
This event indicates that a file required by an application is missing. SideBySide basically allows applications that use different versions of a certain module to run separately, each using the module that applies to it. However, in itself, this error is not a SideBySide problem (it simply reports that it was unable to complete a task). There could be many reasons why a file would be missing: applications that are uninstalled and remove some files that are used by other applications, still on that system, hardware problems causing the corruption of the file system (affecting some of the files). A common set of files that seem to be recorded with this message are C runtime files (VCxx). These come with many applications and it is conceivable but some poorly configured software will remove these when uninstalled (leaving other application without the required modules).
This event may occur because the run-time libraries are not installed on the Microsoft Dynamics CRM server. The applications that use side-by-side libraries cannot run without the run-time libraries. See ME923014 to solve this problem.
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.
See ME947379 for additional information about this event.
In my case, installing the "Microsoft Visual C++ 2005 Redistributable Package" solves the problem.
This problem can be related to a bad Sage Line 50 version 2007 install package. Follow the steps to download the Visual C++ Redistributables and then remove and reinstall Sage Line 50 2007.
This event occurs in conjunction with EventID 59 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 Runtime Library Package.
See ME841082 for a hotfix applicable to Windows Server 2003 64-Bit Edition.
|Private comment: Subscribers only. See example of private comment|
|Links: ME841082, ME914061, ME923014, ME947379, EventID 59 from source SideBySide, Microsoft Visual C++ 2005 Redistributable Package|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (3) - More links...|
|Custom search for *****: Google - Bing - Microsoft - Yahoo|
Send comments or solutions
- Notify me when updated