Conozca más acerca de las soluciones de análisis de Intergraph y COADE.
You need to verify the following:
Make sure you don't have the DWG file already open in AutoCAD. If some other process already has the DWG file open, CAESAR II can't read it.
For additional debugging information, use REGEDIT and navigate to HKEY_CURRENT_USER\Software\COADE, Inc.\CAESAR II\5.10\Options and change "CWXC2 Debug Mode" to a non-zero value. This will dump three "hmf" files to the root of Drive C (dwgmodelkey.hmf, dwgviewkey.hmf, and dwg_c2key.hmf). Send these to Intergraph for analysis.
This is a known Microsoft problem. Here is a link to the Knowledge Base Article that discusses this issue. One known work-around is to avoid the use of OPENGL driver. In CAESAR II, you can change to "Basic Windows Video" in the "3D Viewer Settings" tab of the configuration module.
Windows Vista doesn't contain all of the necessary DirectX 9 dlls to run the HOOPS Direct3D driver. The HOOPS driver references d3dx9_xx.dll files, such as d3dx9_32.dll or d3dx9_34.dll. These DLLs are not currently distributed with Vista. You can either copy these DLL files over from XP into your System32 directory, or try downloading them from Microsoft at (DirectX 9 DLLs).
Verify that you have successfully transferred the license data from the old HASP ESL to the new HL ESL. Detailed transfer instructions were provided as the first two pages of the Update Notes. If these notes are not available, you can find these instructions in the User's Guide, which can be found in the \caesar\c2_docu directory.
Typical error codes which indicate this condition are #7 and #31.
The solution to this involves making a change to the System Registry.
A Microsoft Security Update was installed that disabled access to CHM files on network drives. The Microsoft Knowledge Base articles that explain this issue and the fixes are #896054 and #902225. This second article can be viewed by clicking here.
The installation of the software failed to properly register a DLL with the Windows system. To correct this problem, bring up the [Start\Run] box and issue the command:
Note, change "c:\caesar" as necessary for your particular installation.
One cause of this has been traced to a problem with the Windows XML Parser. An update for this parser is available from Microsoft at http://www.microsoft.com/downloads/details.aspx?FamilyID=28494391-052b-42ff-9674-f752bdca9582&DisplayLang=en. Download the "msxml3.msi" file and run it. Then try to put the patch/build/update on again.
Additionally, review this link (http://support.microsoft.com/kb/898628) which describes a behavioral change in the Microsoft Installer, which can also cause installation problems.
Windows periodically cleans up (empties) temporary folders, which is why the installation wizard may prompt for this file. The procedure for acquiring this MSI file from the original CD is as follows:
This is a generic error message displayed by InstallShield. There is no way to tell what went wrong without reviewing a log file of the installation process. To generate a log file, bring up the [Start\Run] box and issue the command:
"e:\caesar ii 5.00\setup.exe" /v"/L* c:\temp\logfile.txt"
Note, change "e" to your CD-Rom drive, and "c:\temp" as necessary for your particular system.
If the log file reports an error with the file msxmlx.inf, the installation failed due to a problem installing MDAC 2.8, because a file has been erroneously flagged as "read only." To correct this problem and permit the installation of CAESAR II, navigate to the c:/windows/inf directory and issue the command "attrib -r msxmlx.inf [Enter]." Now, restart the CAESAR II installation; CAESAR II should install fine.
The installation is attempting to register a DLL, which unfortunately needs access to the ESL for success. Since the ESL driver isn't loaded, and the 5.00 ESLs are being shipped blank, this registration will not be successful. Finish the installation, transfer the license data to the new HL ESL, then run "c:\program files\coade, inc\caesar ii 5.00\netuserc2.bat," which will register the DLL.
Upgrade your version of VovoView. This can be downloaded from http://support.alias.ltd.uk/products/downloads/voloviewexpress/vve201setup.exe.
This error usually means there is some kind of disconnectivity (as defined by Isogen) in the model. Isogen assumes the models are designed for construction, which isn't necessarily true from a CAESAR II stand point. (For example, this error can be caused if the pipe diameter suddenly changes in a line without a reducer.)
Another cause of this error is when the file name is too long. Isogen has a limit of 120 characters, so make sure your paths are not too deep.
There is a log file that is generated below your "temp" folder, in %Temp%\Isometricdir\IsometricProject\IsometricStyle\Messages\IsometricStyle.mes. The file is a little cryptic, but it may provide a clue as to the source of the problem. Open and review this text file before exiting the Isogen interface, since this file is deleted upon exit.
The installation of Isogen assumes most of the files will be installed to Drive C. Additionally, some directory names have been assumed, such as "Common Files." To correct this problem, find the file sysconfig.mdb, which should be in %system drive%\Program Files\Common Files\Alias\Data. Now ...
1a) Open "RegEdit and navigate to HKEY_LOCAL_MACHINE\Software\Alias\Project Manager.
b) Once at this key, change the path for FontPath, IsoDirListPath, "SysConfigPath, and TemplatesPath so they all point to the same path location where sysconfig.mdb resides.
2) This problem can also be caused by installing an earlier version of CAESAR II after installing Version 5.00. The earlier version will register its own copy of "pipedll.dll," which is incompatible with Version 5.00 (in Windows, only one copy of a particular DLL can be registered). The solution is to manually register the "pipedll.dll" in the "Version 5.00" installation directory. The easiest way to accomplish this is to run the "NetUserC2.bat" file in the "Version 5.00" installation directory.
The installation of the software attempted to register pipedll.dll with Windows. This registration process failed because access to a valid ESL is required (which isn't available during the installation of Version 5.00). To correct this problem, register this DLL manually. There are two ways to accomplish this registration:
1) Using Windows Explorer, navigate to the CAESAR II program directory, find the file netuserC2.bat and double-click it, or
2) Use the [Start\Run] box and issue the command "regsvr32 "c:\program files\coade inc\caesar ii 5.00\pipedll.dll." This path may be different if you installed CAESAR II to a different location.
Note, both options assume you have the necessary rights to register a DLL. If this is not the case, you will need assistance from your IT Department.
Unfortunately, ISOGEN attempts to create a file in C:\Documents and Settings\All Users\Application Data\Alias, which many users will not have access rights to. The solution to this problem can be found in the Alias FAQ at http://www.alias.ltd.uk/support/FAQs/I-Configure.htm.
Many users have had issues with color plots being unreadable on their "black and white" printers. This can be attributed to the inability of the printer (or the printer device driver) to properly emulate color. As a result, CAESAR II now defaults to, and forces "black and white" printing. If you want color plots, and you really have a color printer, then turn this option off. Go to the CAESAR II configuration, then "3D Viewer Settings." Near the bottom of this dialog is the "Force Black and White Printing" option. Uncheck this option to obtain color plots.