CM4D Application Troubleshooting

CM4D Application Troubleshooting

Click here to see this page in full context

CM4D Application Troubleshooting

Topic ContentsTopic Contents

CM4D
DataSmith
DataUtility
DbConnect
EventSmith
SiteManager

CM4D

Area	Issue	Checks	Solution(s)	Help Topics
Database Connection	On startup, the following message appears before the application shuts down: CM4D session ending! Unable to connect to site.	Check the connection information in DbConnect.
		Check that the current user has required privileges in Site Manager to run CM4D.
		Re-run the Site Grant.sql and/or the Grant.sql scripts on the updated database.
Export	Export Data Format Issues - Issues have been reported with the export functionality throughout the package. Most of these issues are due to the migration to UTF-16 encoding with v23 and beyond.		Some of these issues are more of a Microsoft problem than CM4D. CM4D is writing out a proper BOM in the export funtions, but tools like Excel don't seem to be handling it properly.	https://docs.microsoft.com/en-us/windows/win32/intl/using-byte-order-marks
Views	Model missing from view.	Are Cutting Planes enabled?	If you load a part that is located far from the currently set cutting plane, you may not see the model at all. Either zoom in/out until you see the cutting plane boundaries, or reset the cutting planes and perform a Zoom Max on the View.
Views	Model missing from view.	Is the image scale set/correct?	Confirm the scale (even the default) is correct for the size of the model and the units used for the image vs the units of the CM4D document.

DataSmith

Area	Issue	Checks	Solution(s)	Help Topics
Headers	Insert Header Preprocessor not displayed in file. Add files with Preprocessing "Insert Header". Header is not created, and highlighting is not being displayed. DataSmith config has the 'Insert Header' preprocessor set, and a data file is added.	Check to see if that data file is currently opened somewhere else, perhaps already added to another Config.	Once the data file is removed from all other Configs, try re-adding that data file.
Exception on Startup	Message Queue service is not available. The following exception message appears on startup: ‘Message Queue service is not available.’	Check if Message Queuing service is running.	Start the Windows Service, 'Message Queuing'.
Exception on Output	Key Not Found. The following exception message appears when outputting data: ‘KeyNotFound: The given key was not present in the dictionary.’	Check if user running Results services has proper permissions for MSMQ Queues.	Start the Results Services and the the logon user has at least the Send Message permission.
	Argument Null Exception. The following exception message appears when outputting data: ‘ArgumentNullException: Value cannot be null.’	Check if Message Queuing service is running.	Start the Windows Service, 'Message Queuing'.
	Destination queue could not be found. The following exception message appears when outputting data: ‘The destination queue could not be found. The queue does not exist, or you do not have sufficient permissions to perform the operation.’	Check if MSMQ Queues are created for ATS.CM4D.Conestoga (Computer Messages > Services and Application > Message Queuing > Private Queues).

DataUtility

Area	Issue	Checks	Solution(s)	Help Topics
Errors on Commit	Key Not Found. Delete or update data and Commit changes. Exception message: ‘KeyNotFound: The given key was not present in the dictionary.’	Check if user running Results services has proper permissions for MSMQ Queues.
	Destination queue could not found. On delete or update data, on commit the following exception message appears: ‘The destination queue could not be found. The queue does not exist, or you do not have sufficient permissions to perform the operation.’	Check if MSMQ Queues are created for ATS.CM4D.Conestoga (Computer Messages > Services and Application > Message Queuing > Private Queues).
	Failed to send message. On delete or update data, on commit the following exception message appears: ‘Failed to send message to address.’	Check if Message Queuing service is running.

DbConnect

Area	Issue	Checks	Solution(s)	Help Topics
Failed Connection	Failed to open datasource. On Test Connection, the following error message: ‘Failed Site DB connection: Failed to open datasource.’	Check if Database Name is correct.
		Check if Server Name is correct.
		Check if Database User ID is correct.
		Check if Database Password is correct.
	Internal exception. On Test Connection, the following error message: ‘Failed Site DB connection: Internal exception!’	Check if the set Connection Type is correct for the database.
	Failed to open CM4D.4ds. After modifying settings, click Apply or OK. Error message ‘Failed to open CM4D connection file.’	Is this the first time you have run DbConnect, following either an upgrade or new installation?	Run DbConnect as Administrator, then try to open the 4ds file again.
Wrong Schema	Wrong Schema version. On Test Connection, the following error message: ‘Site Datasource Schema Version is xx it must be xx.’	Is the database upgraded to the currently installed version?	Update Site Database to correct Schema Version.

EventSmith

Area	Issue	Checks	Solution(s)	Help Topics
Notification Email	No Routine name is included in the email notification.		This is a valid result, depending on the data in the relevant DataSet. Some DataStacks and Transposed DataSets cannot resolve the Routine label.

SiteManager

Area	Issue	Checks	Solution(s)	Help Topics
Db Error	Database error Syntax error or access violation. On running SiteManager, the following message appears: DataBase Error! Error(s): Database record set failed to prepare data source load command: Site DataSource {call LoadGroupIDs(?)} #: 1 Source: "Microsoft OLE DB Provider for SQL Server" Description: "Syntax error or access violation" Closing Site Manager!	Was the database version recently updated?	Re-run the Site Grant.sql and/or the Grant.sql scripts on the updated database.
Failed Connection	Failed to open datasource. On Test Connection, the following error message appears: ‘Failed DB connection: Failed to open datasource.’	Check if Database Name is correct.
		Check if Server Name is correct.
		Check if Database User ID is correct.
		Check if Database Password is correct.
Import/Export	Import/Export Users from the Users tab does nothing.	Is Microsoft Excel is installed on the machine running SiteManager?	Run SiteManager on a machine with Excel, or install Excel and then try the import/export again.
Wrong Schema	Wrong schema version. On Test Connection, the following error message appears: ‘CM4D DataSource Schema Version is xx it must be xx.’	Is the database upgraded to the currently installed version?	Update CM4D Database to correct Schema Version.

Can we improve this topic?