Link to home
Start Free TrialLog in
Avatar of TransBind
TransBind

asked on

Error: The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found.

I get a weird error below when the constructor is invoked. The error started to appear when we migrated our web application to a new set of servers.

The description for Event ID ( 0 ) in Source ( .NET Runtime ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: .NET Runtime version 1.1.4322.2300- Setup Error: Failed to load resources from resource file

Please check your Setup.
ASKER CERTIFIED SOLUTION
Avatar of Christopher Kile
Christopher Kile
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of TransBind
TransBind

ASKER

Maybe this will help ... It is a compiled web application, there are no resx files only (dll, aspx) files ... It is running under win 2003 server cluster environment (session sticky) iis 6.0 and sql server 2000.
No .resx files??  I consider that odd, but we don't do more than one locale, so we go with default management of resources.  From where are you loading your resources, to the best of your knowledge?
For our final release we compile all of our applications and release only .dll files and .aspx files into production. To the best of my knowledge when you compile a project the compiler will compile these files into binary files with the .resource extension, and then the linker will put these into the final EXE or DLL.
In that case, my guess is someone screwed up and didn't include the resource argument when they linked the DLLs for your distribution, or that the DLLs that contain the resources are not available to the Web application (perhaps they were installed to the wrong directory).