This ensures that the correct msvcr90.dll is loaded by the Engine application. Add the following XML into the app.manifest: In Visual Studio, Add New Item > Application Manifest File (app.manifest). Solution or WorkaroundĪn application manifest should be added to the Engine application to ensure the correct msvcr90.dll (required by Python) is loaded. Cases reported to Esri show that this configuration is sometimes seen with two widely used software packages: LANDesk (C:\Program Files (x86)\LANDesk\Shared Files) and the Intel Management Engine’s iCLS component (C:\Program Files (x86)\Intel\iCLS Client\). If their install and configuration adds the program’s folder to the PATH environment variable, the machine can trigger this issue in ArcGIS. The msvcr90.dll C runtime library is installed and used by many third-party programs. Viewing maps or layers with Python labeling expressions, opening the Python window, and working with geoprocessing tools can all cause Python to load, which can trigger loading the incorrect Microsoft C Runtime Library version 9, msvcr90.dll. The duplicate copy is typically exposed to the application when a folder with a copy of msvcr90.dll exists in the PATH environment variable. This error message occurs when the application encounters duplicate copies of the Microsoft C Runtime Library version 9, msvcr90.dll. This issue also affects ArcEngine version 10.4.1 for the. However, if the process has a dependency on the Microsoft C Runtime Library version 9, the process may crash. 1000, time stamp: 0x4d83e310įaulting module name: MSVCR90.dll, version: 9.4940, time stamp: 0x4ca2ef57įaulting application start time: 0x01ced57b282ee704įaulting application path: C:\Program Files (x86)\Microsoft Office\Office14\WINWORD.EXEįaulting module path: C:\Windows\WinSxS\x86_1fc8b3b9a1e18e3b_9.4940_none_50916076bcb9a742\MSVCR90.After clicking OK to dismiss the error message, the application typically continues to run and function normally without crashing. any ideas?įaulting application name: WINWORD.EXE, version. Going forward I would like to change the template path on all files to the new server. This should temporarily resolve the issue. My DNS entry for the hostname of the old server to point to the new server. Since there is no further need for the old server I changed The question is resolving for all files going forward. I updated the path under the development tab in word and it appears to have fixed the issue. I have a few users that were receiving the error below and in grinding away at a solution I noticed this was tied to my template path printing to an old File and Print Server whereĪ template used to reside.
0 kommentar(er)
