Failed to Create the DataGlobal Object

Issue:

The Database Communicator is running but no jobs are being tracked in the Job Manager or the Client is running but the user is not receiving any Pop Ups. The Database Communicator Error log has entries similar to these:

  • Failed to create the PAData object.
  • Failed to initialize the PA6 licensing object.
  • Failed to create the DataGlobal Object
Cause:

These errors are thrown when the Database Communicator can't instantiate the COM objects in the PA6 data layer. This can be caused if the pa6data.dll file didn't register properly.

Solution:

There are three possible solutions. Try them in the order they are listed.

  1. Check the location of the pa6data.dll file. It should be located in <INSTALL_PATH>\Print Audit Inc\Print Audit 6\Common\
  2. Manually re-register the file. Open a DOS (command prompt). Change to the directory shown above. Type "regsvr32 /u pa6data.dll" (without the quotes) and hit enter. You should get a prompt "DllUnregisterServer in pa6data.dll succeeded". Click OK. Type "regsvr32 pa6data.dll" (without the quotes) and hit enter. You should get a prompt "DllRegisterServer in pa6data.dll succeeded". Click OK.
  3. Uninstall and then re-install the Print Audit components.
How did we do with this article?