Description
There was a problem connecting to the CopyMinder website.
The error usually appears with a second number (the extended error), e.g. 7/12029. The extended error number is a Windows specific error number. A full list of these errors is provided by Microsoft here: http://support.microsoft.com/kb/193625
Solution
Check your computer can access the internet ok, specifically http://primary.copyminder.com and http://secondary.copyminder.com.
We also have http://www.copyminder.com and http://www.microcosm.co.uk as backup servers, but access to these shouldn't usually be required.
Specific Extended Errors
12029
This means a connection to our server could not be established. This can be due to the internet connection being down, or the presence of a web proxy on the network which is blocking access to our servers. In the latter case please ensure the proxy is either reconfigured to allow access or bypassed completely.
12168
This extended error has been seen to occur with the "Untangle" firewall product when it is configured to block direct connections by IP address. Untangle must be configured to allow direct connections by IP address.
Description: Unable to access the Internet.
Solution: There are two possible causes of this error: failed proxy server authentication or blocking by a firewall.
Proxy Servers
Home users are unlikely to use proxy server authentication.
If you have a proxy server that requires authentication then CopyMinder will prompt you to enter the appropriate password. If you fail to provide the correct password, it will give this error.
Firewalls
Your machine probably includes one or more firewalls to prevent unwanted Internet access to/from your machine. Modern versions of Windows include a firewall, people install 3rd party firewalls (e.g. ZoneAlarm), routers and modems may also include firewalls. In most situations, these cause no problems for CopyMinder. However, if a firewall does block access to the Internet for CopyMinder, you will get this error.
If your Internet browser can access this web page from the machine giving this error then firewalls in hardware outside your PC (e.g. routers and modems) are not the cause of this error.
The Windows firewall that Microsoft provides has never been known to block CopyMinder.
Some third party firewalls have facilities to block access to certain web sites. The default settings for these are usually to allow all access unless you explicitly specify otherwise so they should only be a problem if you have instructed them not to allow access to this web site (www.copyminder.com). If you have any concerns about allowing access to this web site, please look at our Privacy Policy.
Some third party firewalls have facilities to block certain applications from accessing the Internet. These are the most likely cause of this error. If your Internet browser can access www.copyminder.com then you should check the firewall settings to ensure that the application you are running is in the list of permitted applications and not in the list of restricted applications.
You could confirm that a particular firewall is causing the problem by temporarily disabling the firewall. Remember to re-enable it afterwards.
Description: Access to the Internet not achieved.
Solution: This is because you clicked Cancel when prompted to connect to the Internet.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Invalid Product Key specified.
Solution: Please contact your Software Supplier for a valid Product Key.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: An error occurred trying to access the CopyMinder web site.
Solution: Click on the 'Display Data' button in the error dialog. This will display the data returned to your program and may give you an indication as to why Internet access is not possible. CopyMinder copes with most Firewalls and Proxy Servers but it is possible that they could cause this error. Contact your Software Supplier for assistance.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
The data returned from the CopyMinder web site to the user's machine was corrupt.
Solution:
Please send your software developer your .cm.log file (See here for instructions on finding the .cm.log file.).
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description:
Solution: Contact your software supplier. They need to make the installation program copy the
Solution: If developing in Delphi, please check that you are using the correct object module. Some versions of Delphi require a Unicode file. cmd.obj is non-unicode, cmdu.obj is unicode
The <program name>.cm file can be in a number of possible locations.
From release 46 of the .cm file onwards, CopyMinder looks in the following locations for the .cm file:
- If there is a <program name>.cm.ini file in the same folder as the protected program and it contains a Path variable, then it will look for the .cm file in that path.
- If the API method of protection was used and the CM_SetPath function has been called then it will look in the specified path.
- It will look in ProgramPath, i.e. the path containing your protected program
- It will look in ProgramPathcm where ProgramPath is the path containing your protected program
- It will look in APPDATAdidProdCodecm where APPDATA is a variable specified in the Windows Environment, did is your unique CopyMinder Developer ID and ProdCode is the Product Code you specified for this product (e.g. C:Documents and SettingsUser1Application DataAABCcm).
- It will look in ALLUSERSPROFILEdidProdCodecm where ALLUSERSPROFILE is a variable specified in the Windows Environment, did is your unique CopyMinder Developer ID and ProdCode is the Product Code you specified for this product (e.g. C:ProgramDataAABCcm).
Prior to release 46 of the .cm file, CopyMinder looks in the following locations for the .cm file:
- If there is a <program name>.cm.ini file in the same folder as the protected program and it contains a Path variable, then it will look for the .cm file in that path.
- If the API method of protection was used and the CM_SetPath function has been called then it will look in the specified path.
- It will look in APPDATAdidProdCodecm where APPDATA is a variable specified in the Windows Environment, did is your unique CopyMinder Developer ID and ProdCode is the Product Code you specified for this product (e.g. C:Documents and SettingsUser1Application DataAABCcm).
- It will look in ALLUSERSPROFILEdidProdCodecm where ALLUSERSPROFILE is a variable specified in the Windows Environment, did is your unique CopyMinder Developer ID and ProdCode is the Product Code you specified for this product (e.g. C:ProgramDataAABCcm).
- It will look in ProgramPath, i.e. the path containing your protected program
- It will look in ProgramPathcm where ProgramPath is the path containing your protected program
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Unable to access <program name>.cm.
Solution: Check that you have full access rights to the path containing this file, that the file's attribute is not set to ReadOnly and that it is not currently being accessed by another application.
Description: Error reading <program name>.cm.
Solution: Please contact Microcosm for assistance with this error.
This error indicates a problem reading the .cm file from the disk. The file has been found and opened with read access successfully, but the actual read of data from it fails.
If a filesystem check and a surface scan both indicate no errors, then it is possible that some kind of system protection software (e.g. anti-virus, anti-malware) is interfering with file accesses, and this should be temporarily disabled to check if it is the source of the error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: The program is using the CopyMinder API protection method but has not actually been protected yet.
Solution: Run CopyMinder.exe to add protection.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: A successful protection check has not been completed prior to another CopyMinder API function.
Solution: Please ensure that CM_CheckProtection is called and is successful before using othe API functions.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: This file format is not supported by the Shell protection method. Only PE format .exe files can be protected using the Shell method.
Solution: Use the CopyMinder API method instead.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description snmpapi.dll was not found. This file is included with all versions of Windows except for Windows 95.
Solution For Windows 95 installations, you need to install Windows Sockets 2.0. You can get this from http://support.microsoft.com/kb/182108/EN-US.
Description: CopyMinder was unable to locate or access the source file.
Solution: Please check that the file exists and is not being used by another process (e.g. currently running).
Description: Unable to write to the destination file.
Solution: The destination file is probably running or in use by another application. Close it!
Error A443 means that the PE/COFF checksum of a file being shell protected could not be updated. We have had a single report of this happening when Avast anti-virus is in use, as it blocked the creation of the protected output file.
The solution is to re-configure the anti-virus software to stop this happening, for example by excluding the output directory from scanning.
Description: Error creating the CopyMinder .cm file.
Solution: Check that the "Output pathname for protected program" is a valid name and that you have full access rights to the folder.
Description: Error writing to the CopyMinder .cm file.
Solution: Check the access rights to the "Output pathname for protected program".
Description: Error creating a registry key.
Solution: Please contact Microcosm for assistance with this error.
Description: Error reading a registry key
Solution: This error can occur in copyminder.exe if the installation was copied from another computer, rather than running CMSetup.exe to install the CopyMinder software onto the computer you are trying to use CopyMinder on. It should never occur at the end user of protected software.
If this did not solve the error, please contact Microcosm for assistance.
Description: Error writing a registry key
Solution: Please contact Microcosm for assistance with this error.
Description: Invalid path specified for "Output pathname for protected program".
Solution: Check that the Output Path you specified is correct.
Description: Error creating folder.
Solution: Please contact Microcosm for assistance with this error.
Description: The specified drive letter is invalid.
Solution: Check that the drive letters given in the Input and Output paths are valid.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Error creating a thread.
Solution: Please contact Microcosm for assistance with this error.
Description: Error opening .CMP file.
Solution: Please ensure the .cmp file exists.
Description: .CMP file is corrupt.
Solution: Please contact Microcosm for assistance with this error.
Description: .CMP file is corrupt.
Solution: Please contact Microcosm for assistance with this error.
Description: The .cmp file you're trying to open was created with a newer version of the CopyMinder SDK.
Solution: Use the latest version of the CopyMinder SDK to open the .cmp file.
Description: Error saving .cmp file.
Solution: Check that you have write access to the location you're trying to save to.
Description: Error saving CMP file.
Solution: Check that you have write access to the location you're trying to save to.
Description: Unable to create thread.
Solution: Please contact Microcosm for assistance with this error.
Description: CopyMinder already running
Solution: Close all instances of CopyMinder then try again.
Description: Unable to allocate memory for .cm file
Solution: Free some system memory by closing unwanted applications or install more RAM in your machine.
Description: Unable to allocate memory for .cm file
Solution: Free some system memory by closing unwanted applications or install some more RAM in your computer.
Description: Error downloading the .cm file from website.
Solution: Please check you are able to access the Internet, and the CopyMinder website in particular using your Internet browser.
If you get error A482/0/705/6/2 then your Developer ID/Password pair are incorrect. Please do the following:
- Go to the Options menu in the CopyMinder SDK (CopyMinder.exe)
- Un-tick "Remember Developer's ID and Password"
- Exit and re-start the Copyminder SDK
- Re-enter your CopyMinder Developer ID and password when prompted to do so
If you are using SDK version 4.4 or later to protect a .NET program and you get eror A482/0/843/0 then your DID is not set to use version 62 or later of the .cm file.
If you are using SDK version 1.6 and get error A482/0/9705/6/2, you need to upgrade to a later version.
If you are using a version of the SDK prior to 2.7 and get error A482/0/8, you also need to upgrade to a later version.
The latest SDK can be downloaded from here
If you get error A482/0/784/... then the name of the program you specified in the Output Pathname field differs from the name of the protected program specified on the web site for this Product Code.
Error A482/0/7 indicates that Internet access was unavailable.
Error A482/0/843/0 means that you're trying to protect a .NET program using SDK 4.4 or later but your account is configured to use version 61 or earlier of the .cm file. Version 62 or later is required for this to work. Please contact Microcosm for support.
Description: Invalid characters found in Product Code.
Solution: You cannot use ` $ ' " = , or ). Please use alternative characters.
Description: User cancelled.
Description: You have chosen to use the API method but the CopyMinder Object module (cm.obj) has not been linked into the program to be protected.
Solution: Consult the Linker for your programming language to see how to link in the appropriate CopyMinder .obj module. If you are protecting your program using cm.dll, remember to specify the name of the dll when adding protection rather than the .exe file.
Description: Error downloading CMInstall.exe from the Copyminder website.
Solution: Please ensure that you have a working internet connection.
Description: CopyMinder.exe was unable to save CMInstall.exe in the 'Output pathname for protected program' that you specified.
Solution: Terminate any existing CMInstall.exe that may be running. Ensure that you have full access rights to the specified path.
Description: You are protecting a file which has a newer version of the .obj or cm.dll than you are authorised to use.
Solution: You should either link in an older version of the .obj or cm.dll files or ask Microcosm to put you on to a later release of the .cm file.
Description: This program has not been protected with CopyMinder yet.
Solution: Please protect it using the CopyMinder program (CopyMinder.exe).
Description: GetDlgItemText failed
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: CopyMinder was unable to create the <program name>.cm.dir directory. This is probably due to the user not having sufficient access rights. Please also see the important notes below for other possible causes.
IMPORTANT NOTES:
(1) The anti-virus software "Threatfire" which is available standalone and as part of the PC-Tools suite will cause 508 errors if its service is running while a protection check is made. The only solution at present is to disable the Threatfire service from Control Panel / Administrative tools. Version 50 avoids this problem. The normal automatic upgrade of the .cm file will not work as the error prevents the new .cm file from being saved. If the Threatfire service is disabled then the protected program will run correctly and can upgrade itself.
(2) This error can also occur if using Advanced Runtime Protection with the shell method on versions of the .cm file prior to 47. In this case the user must be provided with a new copy of the protected program and .cm file using cm file version 47 or later. The normal automatic upgrade of the .cm file will not work as the error prevents the new .cm file from being saved.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: CopyMinder was not able to create a file in the .cm.dir directory.
Solution:
The most likely cause is that you do not have sufficient access rights to create the file. If so, you need to change your access rights.
Alternatively, the directory may be corrupt. Try running the Windows Chkdsk utility to check and repair any corruption.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Computer hardware information changed
Solution: We have found that one possible cause of this is that a removeable network adapter (e.g USB wifi, PCMCIA / PC-card or tethered mobile phone) that was present when the software was installed has now been removed.
To avoid this error in future, activation should be done with any removeable network devices removed from the computer. Other USB devices should not cause this error. Also, please ensure that at least version 52 of the .cm file is in use.
If this is does not solve the problem, please contact Microcosm providing the .cm.log file for the affected installation.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: LoadLibrary failed
Solution: Please contact Microcosm for assistance with this error.
Description: GetProcAddress failed
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Error writing to the
Solution: This is probably because the file or directory it's located in is read only. Please check this and try again.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: The protected program has reached the expiry date specified by the software supplier.
Solution: Ask your software supplier to change the expiry date.
This error occurs when the date on your computer is later than the expiry date so check that your computer's clock is set correctly. Also check that it is set up for the correct international time zone.
Developers: You may have accidentally set the value (or default value) for 'Days till expiry from first installation' to zero when you meant 'no limit'.
Description: You are trying to run this program more times than your Software Developer has allowed.
Solution: Please contact your Software Supplier.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Unable to display a dialog.
Solution: If this is a network installation, the most likely cause is that the .cm file in the folder containing CMNet.exe has been overwritten with a new copy. If so, you should terminate and re-install CMNet.
Description: You hit 'Cancel' when prompted for a Product Key.
Solution: Enter a Product Key and don't press cancel 
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: The path of the program is too long.
Solution: Please install your program into a shorter path.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Problem creating/writing to a file needed for a CopyMinder protected program to run.
Solution: Please ensure you have full access rights to the directory you are trying to run your program from.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Error automatically downloading new CopyMinder protection file.
Solution: Please check your Internet connection.
This error can also occur if all the following is true:
* Your existing .cm protection file is release 36 or earlier.
* Your program is protected to require release 37 or later.
* The .cm file has not been used before.
Ask your software supplier if this might be the case. In this case the software developer should supply a newer (v.37 or later) .cm file for the software so that installation and activation may proceed.
Solution: Disable or remove Bit Defender
Bit Defender 2012 injects javascript and css into webpages that are accessed, whether through a browser or directly by the CopyMinder protection check. This causes the structure of the page to be changed and consequently the download of the page containing the update version of the .cm file to fail when an automatic upgrade is attempted during a protection check.
If you wish to download and install the CopyMinder protection file manually, please go to the link below and follow the instructions:
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: CopyMinder was unable to write to the Windows Registry. This is almost certainly an access rights issue
Solution: Re-install the protection using the CMInstall.exe program
If this does not solve the problem, please send us the .cm.log file.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Unable to decrypt activation code
Solution: If you are using the Manual Activation method, please check the activation code is correct.
If you are using not using the Manual Activation method, it could be because you are using a program protected with a very old version of CopyMinder.
Description: There was an error setting the clock on the user's computer. Either they specified a date earlier than 2003 or they do not have sufficient privileges to set the clock.
Solution: Try setting the clock on the computer using the normal Windows facilities. Remember to set the time zone correctly.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: This means that your computer's clock is out by more than an hour compared to our web server's.
Solution: Please check the time and date of your machine and adjust as necessary.
Please also check that the international time zone setting is correct.
Description: The clock on your machine has gone backwards.
Solution: You should do one of the following:
1. If you have put your clock backwards, you should put it forward to the correct time.
2. If you have put it forwards just a bit and then back to the correct time, you should wait until time catches up.
3. You should re-install your application or replace the .cm file with the original copy.
Description: The CopyMinder Network Path you specified either does not exist or you do not have sufficient access rights to it.
Solution: Please check that the CopyMinder Network Path exists. If it does then check that you have sufficient access rights to it. CopyMinder protected programs running over a network, require full read/write access to this directory.
Alternatively, if the CopyMinder Network Path is on the local computer and stored in the .cm.ini file as a UNC type path (e.g. \machinedirectory) then the 581 error will be given if the LAN cable is unplugged, even though the path should resolve locally. This is because Windows will not resolve UNC pathnames if the computer is not connected to the network so cannot access files this way without a working network connection.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Unable to delete file in .cm.dir/dat
Solution: This error means CopyMinder was unable to delete a file in the <program name>.cm.dir/dat directory. The usual reason is to do with file access rights.
The most likely cause of this is that they are using multiple user logins, probably under Vista. Using CMInstall.exe should solve any problems to do with access rights.
Alternatively, their directory could have become corrupt. They should run the Windows Chkdsk utility to detect/repair any problem.
Description: CopyMinder was unable to delete the "[programname].cm.dirdat" directory.
Solution: Please check that you have the appropriate access rights.
If you get this error and you have full access rights to this directory, please list all the files in that directory (including ones with the Hidden attribute set) and send it to Microcosm.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Unable to create a directory.
Solution: Error 611 means we could not create a sub-directory off the directory containing the .cm file. This is probably to do with access rights.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: You hit the 'Cancel' button so the program has aborted.
Solution:
Description: An error occurred writing to the .cm.ini file.
Solution: Please make sure you have write access to the folder containing the .cm and .cm.ini file.
Description: An error occured writing to the logfile.
Solution: Please ensure you have write and read access to the directory where the program's exe file is.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: The .cm file is the wrong one for this program or an attempt was made to do a protection check whilst CopyMinder was already doing a check.
Solution:Close any open CopyMinder dialog boxes, close the protected application and try again. If that does not solve the problem, please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description:
Timeout when trying to perform a protection check from a network client - the CopyMinder Network Server failed to respond.
Solution:
Ask your Network Administrator to check that the CopyMinder Network Server is running on a machine on your network.
The CopyMinderNetworkPath specified in the <PROGRAMNAME>.cm.ini file should be either:
a) An IP address and port (eg, 192.168.1.2:1234) corresponding to the machine running CMServer.exe, or
b) A path corresponding to the shared directory in which CMNet.exe looks for files (this path should correspond to the same location as the path given in the <PROGRAMNAME>.cm.ini file in the same directory as CMNet.exe on the server).
The .cm.log file on the server may reveal why the server is failing to respond.
If the problem persists please contact your software supplier.
Description: Unable to create a file in the CopyMinder Network Path that you specified.
Solution: Make sure that CMNet is running on the CopyMinder network server.
Make sure that the CopyMinder Network Path you specified for the client machine matches that specified for the CopyMinder network server. You can check this by looking in the .cm.ini files of both computers.
Ensure that both computers have full access rights to the specified CopyMinder Network Path.
If there is a <program name>.cm.tmp file present in the CopyMinder Network Path at the time that this error occurs, it may be that CMNet cannot overwrite it. Manually delete the file and try again.
Description: You have reached the limit on the maximum number of simultaneous users of this program
Solution: Contact your supplier and request an increase in the limit or wait until another user stops using the program.
Description: You have not entered a valid Product Key, Activation Code or CopyMinder Path. You should enter one of the following:
- A Product Key. This may have been supplied to you by your Software Supplier and will be of the form X*-XXXX-XXXX-XX (where X* is characters or numbers of varying length).
- An Activation Code. This may have been supplied to you by your Software Supplier and will be a series of numbers such as 43214321523.
- A CopyMinder Path. If this is a network installation, a path may have been specified by your Network Administrator for use by the CopyMinder system. It can be a mapped path (e.g. N:CMPath) or a UNC path (e.g. servercdriveCMPath).
- Nothing. If you enter nothing, a demonstration version of the program may be created (provided the Software Supplier has permitted this).
Solution: Contact your Network Administrator for the CMPath or your Software Supplier for a Product Key or Activation Code.
Description: The .cm file is the wrong one for this program.
Solution: Contact your software supplier for the correct one.
Description: The CopyMinder Path has not been found.
Solution: Edit the
Description: This program is configured for network installation only. It cannot be installed as a standalone system.
Solution: Contact your Network Administrator to install it as a network installation or contact your Software Supplier to get it converted to a standalone system.
This error is most frequently a result of specifying a Product Key on a network client machine instead of the CopyMinder Network Path. For a network installation, when a protected program is first run on a client machine, you should select "Configure as a network client" and enter the CopyMinder Network Path provided to you by your Network Administrator. Your Network Administrator will have chosen a suitable path for this when they installed the CopyMinder CMNet.exe program on your server. Contact your Network Administrator or Software Supplier for assistance.
Description: This program is configured for standalone installation only. It cannot be installed as a network system.
Solution: Contact your Software Supplier to get it converted to a network system.
Description: The .cm file is the wrong one for this program.
Solution: Contact your software supplier for the correct one.
Description: The .cm file is for a different product.
Solution: The protected program has found a .cm file but it has been created using a different Product Code. The most likely cause of this is that your supplier has provided the wrong .cm file.
Description: The .cm file is the wrong one for this program.
Solution: Contact your Software Supplier to get the correct one.
Description: The manual activation code you have entered is invalid.
Solution: Please check that you have entered it correctly.
Description: An invalid manual activation code has been entered.
CopyMinder gives 3 chances to enter it correctly then gives this error.
Solution: Run activate.php again, making sure that the Product Key and Installation Code are correctly specified and check that the resulting activation code agrees with the one you have been entering.
Description: Internet access is required for installation as a Trial.
If you did not specify a Product Key when prompted to do so, CopyMinder will attempt to install the protected program as a Trial.
This error means that you are trying to install the protected program as a Trial without using the Internet. At present, Trials are not possible without Internet access.
The error occurs either because the settings in your <program name>.cm.ini file explicitly forbid Internet access or because CopyMinder was not able to establish an Internet connection.
Solution: Specify a Product Key, if you have one. Check your firewall settings to ensure that access to the CopyMinder web site is permitted.
Description: You aborted a manual activation of this program.
Solution: Please contact your Software Supplier if you are unsure what to do.
Description: This program is configured for internet activation only. You cannot activate it via the activate.php webpage.
Solution: Allow the program access to the internet and it will automatically activate.
Description: The Product Key you entered was invalid.
Solution: This is most likely because the product code associated with this Product Key has been deleted. Please see related article below.
Description: Failed to access both Primary and Secondary CopyMinder Internet servers and no Tertiary server specified.
Solution: There is a problem with your Internet service. If you can access other web sites with your Internet Browser, ask your Network Administrator to check that your Internet Firewall is not blocking access to these sites. If you still have a problem, contact your software supplier or Microcosm.
Description: CopyMinder was unable to write to the Windows Registry.
Solution: Run the CMInstall.exe program which is produced when you build protection using CopyMinder version 3.1 onwards.
If you do not run CMInstall and any of the following conditions are true then you will have a problems running under Vista.
* They have User Account Control (UAC) enabled during installation (you can turn it on/off within 'Control Panel'|'User Accounts').
* They want to install to their Program Files folder (or a sub-folder off it).
* They want to run in non-Administrator mode.
The presence of lines in the .cm.log file on a network server containing the statement "Return Code 684" do not indicate an error condition.
Following a new release of the .cm file, the network server will update itself on its next connection to the CopyMinder servers. Then, as each client connects to it, it will tell them that there is a new version of the .cm file available so they can request it. It signals this by sending them a status value of 684, and records into the log that this has been done. This log file entry is only informational and will appear one for each network client until they are all transitioned to the version that matches the one on the network server.
Description: Client machine is unable to get a new version of the .cm file from a sub-directory off the CopyMinder Network Path.
Solution: If the sub-directory does not exist, manually create it. It should be of the form
Description: Unable to display dialog to prompt for Product Key.
Solution: If this is a network installation, you should terminate and re-install CMNet.exe.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Incorrect parameters passed to www.copyminder.com.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There was a problem connecting to the CopyMinder server's database.
Solution: You might be getting these error because you've recently deleted a product code from the developer webpages. If you didn't mean to delete it we can restore it for you. Please contact us for assistance (we might have to make a small charge depending on how many users need to be restored).
If you're sure you did not delete a product code, but are still getting this error, please contact us for assistance as we will need to investigate the surrounding circumstances to resolve your problem.
Description: There was a problem connecting to the CopyMinder server's database.
Solution: You might be getting these error because you've recently deleted a product code from the developer webpages. If you didn't mean to delete it we can restore it for you. Please contact us for assistance (we might have to make a small charge depending on how many users need to be restored).
If you're sure you did not delete a product code, but are still getting this error, please contact us for assistance as we will need to investigate the surrounding circumstances to resolve your problem.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Invalid Product Key specified.
Solution: If htis error has occured just after your program connected to the CopyMinder server, you will need to re-install your software to get going again.
If you're getting this error because it thinks your Product Key is "
Otherwise, please contact your Software Supplier for a valid Product Key.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Some of the activation details were invalid.
Solution: Please contact your software supplier for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Error accessing Internet database.
Solution:
If you get error 733/33/3, you are probably using a product which your Software Developer has deleted from the CopyMinder database. Please contact your software supplier.
If you get error 733/33/6, you are probably using a Product Key which your Software Developer has deleted from the CopyMinder database. Please contact your software supplier.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Your Software Supplier has disabled this installation.
Solution: Please contact your Software Supplier to get it re-enabled.
Description: Required registration information not recorded
Solution (1): Can happen when a very old .cm file is first run and the user selects "trial installation." This triggers an update of the .cm file to a later version and the registration step is potentially omitted. The solution is for the developer to send them a new protected program and .cm file of at least version 52.
Solution (2): If the <program name>.cm.ini file contains
[Main]
Trial=Neither
ActivationByProductKey=Neither
ProductKey=a valid licence key
before the licence is activated, and CMServer is not running on the network, then the licence will be unable to activated and will cause an error 738.
The ini file options listed above are incompatible with each other, as they tell the protection runtime that it may not use a licence key (thereby implying network client activation is required), then provides a licence key.
Description: This program has been installed or copied too many times.
Solution: Do note that one Product Key should be used per installation. If you keep using the same Product Key for multiple installations you will get this error.
Please contact your Software Supplier to purchase additional licences or to reset the counter.
Sometimes, Software Developers mis-understand the 'Number of suspect installations in the last xxx hours' value on the CopyMinder web site. This is the current number of suspect installations, not the maximum permitted. This number can be reduced to 0 (say) in order to allow a re-install after an error 739.
There are situations we have encountered where this error can be triggered because we detect the hardware of the computer running the protected software as having changed when it has not, due to a change in the way that Windows stores or reports the data. If this corresponds with a change of network environment, such as on a laptop that switches between wired and wifi connections, please look at Settings > Network and Internet > Wifi then untick the "Use Random Hardware Addresses" option if available. it can also be found under individual wifi connections on this page, and some computers don't have this option at all as the underlying hardware does not support it.
Description: Internal error.
Solution: Please contact your supplier.
Description: Your computer system clock is incorrectly set.
Solution: CopyMinder requires that your clock is correctly set up and is within 1 hour of the correct time. The time on your computer is not within this range.
If your computer is displaying the correct time then the problem is that you have the time zone incorrectly set.
Windows includes a time zone setting which is the amount of time that your local time differs from Greenwich Mean Time (GMT) in the winter. GMT is also referred to as coordinated universal time (UTC). You should make sure that this is set correctly on your machine by going to Windows Start|'Control Panel'|'Date and Time'|'Time Zone'.
CopyMinder is not interested in your setting for Daylight Savings.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: The password given to our website was invalid.
Solution: Ensure the password you are using is correct for your DID. If you have forgotten your password then please contact Microcosm.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: You have reached the expiry date specified by your Software Supplier.
Solution: Please contact your Software Supplier to extend or remove the expiry date limit.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: You have reached the limit (set by your Software Supplier) for the number of times this program is permitted to run.
Solution: Please contact your Software Supplier to allow more executions of this program or remove the limit altogether.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: A new .cm file is available but an error occurred trying to download it.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: Your computer's clock is incorrect.
Solution: Please set your timezone and time correctly.
Description: You have tried to install your program as a Trial Installation but your Software Supplier has not enabled Trial installations for you.
Solution: Contact your supplier and ask them to enable Trial Installations for you or ask them to supply you with a Product Key.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: The program you are trying to run has been previously deleted from the web site
Solution: Use CopyMinder to re-protect your program to re-create it on the website
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description: invalid Product Key
Solution: Please ensure you have not mis-typed your product key as the one you specified does not exist.
Description: You are trying to install a manually activated product more than once.
Solution: If you require a second manually activated copy of a program, you need a second product key.
If you had a problem with your first installation, and need to be able to re-install, you need to contact your software supplier and get them to re-set your product key.
Description: There was an error accessing the CopyMinder web sites even though they are working correctly.
A protected program has tried to access:
1. 89.200.137.136 (primary.copyminder.com)
2. 64.22.91.129 (secondary.copyminder.com)
3. 69.10.158.38 (www.copyminder.com)
and failed with all three.
It has then gone to 69.10.158.38 (www.microcosm.co.uk) which has determined that there is nothing wrong with the above servers.
Solution: Confirm that they can access the above servers from their browser.
The most likely explanation is that they have changed their proxy server/firewall settings so that it blocks the CopyMinder servers.
Please try again. If the problem persists, please contact your software supplier or Microcosm.
Description: The Product Key you specified was invalid.
Solution: Please ensure your Product Key is of the form:
X*-XXXX-XXXX-XX
(* indicates variable length).
For example, ABC-1234-1234-12
Description: You are trying to activate (via the Internet) but you have already activated manually. An installation that has been activated via the Internet can be replaced by a manual installation but not vice versa.
Solution: Either get another Product Key from your software supplier or ask them to do a 'manual reset'.
Description: An entry in the Windows Registry has disappeared.
Solution: Avoid doing System Restores to a date prior to the date that you first ran the protected program. If you are using a Registry cleanup utility, please let Microcosm know which one is causing the problem.
Description: A valid email address is required before you can use this software.
Solution: An Email has been sent to the address you registered with us. When you receive it, please click the link in it to verify your email address. If you do not receive the email, simply run the program again for options.
If the address provided goes to a spam prevention service that in turn sends an email reply requiring the sender to click on a link before allowing the recipient to see the email then the mail will never be delivered as the address from which the verification emails are sent, verification@copyminder.com , is unmonitored. The user will need to modify their spam prevention settings to allow the email to be delivered.
Description: A valid email address is required before you can use this software.
Solution: An Email has been sent to the address you registered with us. When you receive it, please click the link in it to verify your email address. If you do not receive the email, simply run the program again for options.
If the address provided goes to a spam prevention service that in turn sends an email reply requiring the sender to click on a link before allowing the recipient to see the email then the mail will never be delivered as the address from which the verification emails are sent, verification@copyminder.com , is unmonitored. The user will need to modify their spam prevention settings to allow the email to be delivered.
This error means that the number of unexpired roaming licences for a network licence key is equal to the number of simultaneous users, so there are no network licences for CMServer to serve.
Description: Your software supplier no longer wishes to use CopyMinder copy protection.
Solution: Ask your software supplier to supply you with a new, unprotected copy of the program.
Description
The user has tried to manually activate a Trial but the Software Developer does not allow this.
Solution
If the Software Developer allows Trials using Internet access then the user could install to a machine that has internet access.
If the Software Developer wants to allow manual Trials then they should do so by setting the default parameters for the Product Code on the CopyMinder Developer's web site.
If neither internet nor manual activations are permitted for Trials then the user should contact the Software Developer.
Solution: If internet access is permitted then check that the internet connection is functioning correctly and that the CopyMinder web sites are not blocked by a firewall or proxy server. Otherwise, perform a manual update.
Description: Activation was not possible either via the Internet or manually.
CopyMinder usually tries to activate via the Internet but gives you an option to activate manually if Internet activation is not possible.
Solution: If your software supplier permits Activation via the Internet then you should check your Internet connection and firewall settings. Click here for further details.
A <program name>.cm.log file on your machine will contain more information about the cause of the failure.
If Internet activation fails and your software supplier permits manual activation but you choose not to do so then you will get this error.
Description: Attempting to write to Secure Data Area before activation.
Solution: Make sure your application has been installed correctly and try again.
Description: CopyMinder was unable to write to your <program name>.cm.dir directory. This is usually a result of insufficient access rights..
--------------------------------------------------------------------------------------------------------------------------------------------------------
Solution: Use CMInstall.exe to install with the correct access rights.
If you do not have CMInstall.exe:
- Delete the <program name>.cm.dir directory and all the files/directories in it.
- Set full access rights for the directory you are installing to.
- Re-install.
Description: Unable to activate as there are no possible activation methods
Solution: examine the
Trial
Product Key
Network client
All of these can be forbidden in the .cm.ini file (see the manual for details), forbidding them all will cause a 910 error. Network client activation is implicitly forbidden with network server type installations (cmnet or cmserver), at least one of either Trial or Product Key must be allowed.
Description
The protected software was unable to create one of it's required files.
Solution
This is most likely to do with access rights so running CMInstall should fix this.
Error 926 means one of the internal modules that the protection check uses couldn't be loaded. The file is called
Possible reasons are lack of permissions on the directory where the .cm file is stored or a virus checker with "real time" protection holding the file open after it is written for scanning, preventing it from then being opened by the CopyMinder runtime code. In this case, the anti-virus software should be set to exclude the directory where the licence files are stored.
Error 928
This error means that a client machine on a network installation running CMServer has been unable to open a TCP/IP socket to communicate with the machine running CMServer. This is very likely a permissions problem.
Description
The protected program was unable to connect to the CopyMinder Network Server (CMServer).
Solution
1) Ensure that CMServer is running on the server.
2) Ensure that no firewalls are blocking the connection between the machine running the protected software and the server.
This error means that the protected software running as a network client licence could not establish communication with CMServer. Please check the IP address and port are correctly configured on the client. These can be found in the <programname>.cm.ini file
Description
The protected program failed to read the response from the CopyMinder Network Server (CMServer).
Cause
The most likely causes for this error are:
- A failure in the network connection between the server and client machines.
- CMServer has quit unexpectedly (crashed).
Solution
Ensure that the network connection between the client machine and the server is still functioning correctly.
Check that CMServer is still running on the server machine.
If you find that CMServer has stopped unexpectedly then please contact your software developer.
The
CMServer /logfile) may also be useful in diagnosing the problem.
Description
The connection to the CopyMinder Network Server (CMServer) was closed unexpectedly,
Solution
Check the status of your network - your network administrator should be able to diagnose any problems.
One possible cause is that there is another process bound to the same TCP port that CMServer is configured to use. Invoking the following command from an Administror command prompt will give a list of all processes bound to ports which can be checked for any duplicate port bindings.
netstat -nab
The output will be extensive so should be redirected to a file to facilitate its examination in a text editor.
Description
The network client's attempt to read data from the server has failed.
Reason
If the extended error is 431:10060 it means that the server took too long to start the protection check. This can happen if the server is very busy.
Description
The CopyMinder Network Server (CMServer) encountered an internal error.
Solution
Ask your network administrator to check the server-side log files for your protected software and for CMServer.
Description
Error 947 means that a new network server .cm file cannot be activated because dialogs are suppressed (because CMServer is running as a Service).
Solution
Step 1) Stop the CMServer service (eg, through the Services management window)
Step 2) Run CMServer (eg, by double-clicking it) - the configuration dialog will appear. Check that it is configured to install/start as a Windows Service.
Step 3) Click the Start button.
Step 4) It should now be able to display any required dialogs to activate the .cm file before installing/starting as a service.
Description
The .cm file used by the CopyMinder Network Server (CMServer) cannot be downgraded to a version prior to 50.
Solution
Contact your software supplier.
Description: Busy timeout. CopyMinder has been trying to open the .cm file for some time without success.
Solution: If the extended error is 240:32 then this means that a protection check is already running. Please check that there is not a CopyMinder dialog open that is waiting for a response from you.
Otherwise, this can be caused by your [program name].exe.cm file being read-only. Please check that it is writable and the directory it is located in has full access rights.
Description: You need to re-boot your machine and run your program again.
Solution: This is only necessary once on any particular machine that has this problem. It should only apply to a small number of Windows 95/98 installations (Microsoft put a file in the wrong directory!).
If you continue to get this error, please go to 'Control Panel'|System|'Device Manager' and check that it thinks the Primary IDE device is ok.
Error 985 means that the licence is awaiting email verification and the user has been prompted to ask if they want the verification email to be resent, then they have cancelled this dialog box.
If you provide your own dialog in this situation via the messages DLL interface and return 3 from your implementation of CM_MSGS_AwaitingEmailVerification() then this will also cause error 985.
Description
The protected program was waiting too long for the Advanced Runtime Protection (ARP) system to initialize.
Solution
This is usually caused by TrendMicro Anti-Virus software preventing the ARP system from working properly. Stop TrendMicro and see if you are then able to run the protected software.
See Also
Error 1202 often accompanies this error.
Description: Upgrading/downgrading the .cm file failed due to a problem transferring the .NET data.
Solution: The extended error number will indicate the reason. See related articles.
Description
Your .cm file is trying to downgrade to a version that does not support protection of .NET programs.
Solution
Contact your software supplier.
Description: There is no description for this error.
This error indicates a problem reading a text string from the licence file. As this is static data, it can be indicative of the file corruption so re-installing the licence should be considered.
We have also had two reports where the Windows default language was German and changing it to anything else solved the problem. We have not been able to reproduce this ourselves, nor have we had other reports from the thousands of other sites running protected software in Germany, so this cause remains under investigation.
Description: There is no description for this error.
Solution: Please contact Microcosm for assistance with this error.
Description
This error number can mean two things:
1. If the error does not have a path appended to it then it means that the CMInstall destination directory does not already exist and CMInstall is unable to create the destination directory.
2. If the error does have a path on the end (e.g. 1005/161/c:abcmyprog.exe.cm.ini) then this means that CMInstall was unable to write a Path= statement to the ini file.
Solution
1. If the CMInstall /p option was used to specify the destination path, check that the /p is followed by a valid path.
If the operating system is earlier than Windows 2000 then ensure that the specified path already has a parent. For example, if you specified c:abcdef, ensure that c:abc already exists.
2. If a .ini file already exists, ensure that it has a valid ini file structure.
Solution: This is most likely to be caused by the user specifying an invalid destination path.
An extended error will have been appended to the error number (e.g. 1011/7). The meaning of this extended error is:
1 - Destination file already exists and they do not want to overwrite it.
2 - Source required but not found.
3 - Destination path not found and they do not want us to create it.
4 - General failure other than Access Denied.
5 - Access Denied
6 - Unable to create destination directory.
7 - Error creating an empty .cm file in the destination directory.
8 - Unable to access destination path for reason other than not found.
Description: The version of the .cm file is too old for this copy of CMInstall.exe.
Solution: Contact your software supplier for a newer copy of the .cm file.
Solution: This is most likely to be the result of the user specifying an invalid destination path.
The Windows error number in the MessageBox indicates the precise cause of the error.
This error message is usually followed by a CMInstall error 1011.
Description: CMInstall was unable to create the directory specified for the CM Destination Path.
Solution: Check that the specified path is valid and that you have the necessary permissions to create a sub-directory in it.
Description: CMInstall was unable to create the Destination Path for the .cm file.
Solution: You probably do not have sufficient access rights to the All Users folder. If installing as a non-administrator, use the /c option with CMInstall.exe (e.g. CMInstall /c). This will install protection for the current user only.
Description
The /c command line parameter (install for current user) is not supported on Vista onwards due to the way in which these operating systems elevate processes to run with higher privileges.
Solution
Use CMInstall to install the CopyMinder protection for all users (the default) instead.
Error 1054
Unknown Machine name
In a network protection environment, the machine name stored in the client .cm.ini file cannot be resolved. This might happen if an old server is retired and a new one set up, but the ini files on the client machines are not updated to reflect this
Cause: Downgrading the .cm file to a version with incompatible encryption.
Solution: Contact your software developer.
Description
Part of the Advanced Runtime Protection (ARP) system included in the Shell method failed to initialize properly.
Solution
There is a known problem where TrendMicro Anti-Virus software prevents the ARP system functioning properly. Stop TrendMicro and see if you are then able to run the software.
See Also
Error 991 usually accompanies this error.
Error 1211.
Description
Part of the Advanced Runtime Protection system (ARP) failed to function properly. ARP is part of the Shell method.
Solution
There is a known problem where TrendMicro Anti-Virus software prevents the ARP system functioning properly. Stop TrendMicro and see if the problem continues to occur.
See Also
Error 1202.
Description
Part of the Advanced Runtime Protection (ARP) system failed to function properly. ARP is part of the Shell method.
Solution
There is a known problem where Symantec EndPoint Protection and Avast! Anti-Virus software "Deep scan" prevents the ARP system functioning properly. If either of these
are present, stop them and see if the problem is solved. If it is, consider excluding the directory containing the protected program from being scanned before re-enabling the AV software.
Description: You get error 1518 when Shell protecting a .NET assembly using the CopyMinder program.
Cause: The assembly you are trying to protect has been strong-name signed.
Solution: CopyMinder protect the assembly before strong-name signing it.
Error 1530 means you are attempting to shell protect a .NET Metro app, which is currently unsupported.
Description
Installing CMServer as a Windows Service has failed.
Solution
This is usually to do with having insufficient permissions to perform the installation. Installing a Service can only be done by an Administrator.
On Vista and Windows 7, being logged in using an Administrator account is not enough. You should start a new command-prompt by finding a Command-Prompt shortcut, right clicking on it, and selecting "Run as Administrator". Now you should be able to run
CMServer /s
and install the Service successfully.
Description
The CMServer Service failed to start.
Solution
Consult the CMServer log file which you can access by running:
CMServer /logfile
Description
CMServer didn't recognize the Product Code that the protected program passed to it.
Solution
Check that CMServer is serving all the products that you expect.
Check the CMServer log file for any errors during the protection check for that product.
To view the CMServer log file run:
CMServer /logfile
from a command prompt.
Description
There are no products left for CMServer to serve.
Solution
This either means that there are no .cm files for CMServer to use, or that after calling a protection check at startup for each product none were successful.
Check the .cm.log file for each product that CMServer serves to see what error occurred.
If you are using CMServer and had manually activated the licence, it may need to establish a connection to our servers but be unable to render the manual update dialog box as it is running as a service. This is one of the reasons we specifically advise against combining CMServer with manual activation. In this case you must start CMServer by double-clicking so it launches on the desktop and the user can interact with it to complete the manual update process and then select to start as a service.
Description
You are trying to install CMServer as a Windows Service, but CMServer.exe is not stored on the system drive.
Solution
Install CMServer.exe on the system drive. The system drive is the drive on which Windows is installed (eg, C:).
Error 1965
ws2_32.dll missing or corrupt
CopyMinder requires the Windows ws2_32.dll file to be present and functional for the protection check to work. If we cannot load it, this error will be returned
This error only applies to 64 bit code and only where there is a network user limit
If an error 1968 occurs in a 64 bit protected program, please ensure that the accompanying <program name>.cm file is present in the directory with the protected program, or the C:\ProgramData\<Developer ID>\<Product Code>\cm . If you specify a different destination directory when calling CMInstall.exe then you should ensure it is present in that directory.
In October 2019 Symantec made changes to it's Endpoint protection product which can cause false detections of SONAR.Heuristic.159 during protection checks in 64 bit applications. The file generating the false positive is <programname>.cm64.exe and since this is unique to each protected application may need to be submitted as a false positive by each software developer. We will assist developers with this process or undertake it on their behalf, upon request.
It is possible that other anti-virus or system protection software might incorrectly detect the <programname>.cm64.exe file as malware, so if this error occurs, please ensure that the licence file directory is excluded from any real-time decection.
Error 1978
File creation error
An attempt to create a file in the same directory as the working copy of the <program name>.cm file failed. File create and write access to this directory is required at run time. If you have used CMInstall with the default options this directory will be a sub-directory from the location specified in the AllUsersProfile environment variable. If you haven\'t used CMInstall, you must.
This error appplies to the 64 bit protection check only
Error 1981
Null pointer
When one of the CM_Get functions was called, a null value was passed for the pointer to receive the return data. This error applies to the CopyMinder 64 bit modules only.
Error 1983
One of the CM_Get functions was called before a protection check had been successfully completed, so there was no data to return.