(For CodeManager 2004-2007 click here.)
My computer was infected with a virus. Now when I try to start CodeManager I get
a message that the Cassini metabase is hidden, or some other file is hidden.
Applies to: CodeManager, CPT Assistant Archives, CPT Changes Archives, all 2007 versions forward (CPT Assistant 1990-2006 forward)
The virus sets the "hidden" property of files in the Program Files and ProgramData folders to on. Resetting the property so the files are not hidden resolves the problem.
To turn off the hidden property for all AMA programs:
If you have Windows 7 or Vista, go to Start, Computer, OS (C:), ProgramData, UltiDev. If you have Windows XP, go to Start, My Computer, Local Disk (C:), Documents and Settings, All Users, Application Data, UltiDev.
Your AMA programs should now work normally.
When I try to start the program I get an error about Access to Path is Denied. If I
click through this another one appears. If I click through enough the Welcome screen appears.
Applies to: CodeManager 2011
This error is caused by Windows User Account Control (UAC) in Vista and Windows 7. Turning off UAC will eliminate the problem.
To turn off User Account Control in Vista:
To turn off User Account Control in Windows 7:
When I try to start the program I get a Page Cannot Be Displayed error.
Applies to: CodeManager 2008-2011
There are two causes of this error. The most common cause is that the local web server is not running normally or did not install properly. The second cause is a firewall blocking access to the web server.
Try restarting the local web server:
Check for the local web server:
If the installation did not succeed:
On the Windows Services List:
If restarting the UltiDev Cassini web server doesn't fix this problem a firewall is blocking the web server. You can get the information you need to configure your firewall for CodeManager from the firewalls.txt file on the CD.
When I try to search I get an error: "The type initializer for 'ApiInitializer' threw an exception"
Applies to: CodeManager 2010-2011
This error occurs because the Microsoft .NET Framework 2.0 or 3.5 has become corrupt. It is resolved by fixing the corruption then repairing CodeManager.
To repair the Microsoft .NET Framework 2.0 and CodeManager:
When installing CodeManager it gives an error: "Error 1001. Exception during commit phase"
Applies to: CodeManager 2010-2011
This error occurs when the installation cannot stop the Cassini web service so it can be configured. It is resolved by manually setting the service so the installation can configure it.
To set the Cassini web server for configuration:
After I have installed CodeManager when I try to start the program it checks for AMA products,
then tells me it is loading, then comes to a Server error in application and says a Runtime error has occurred.
Applies to: CodeManager 2008-2011
This error is caused by a missing or corrupted Visual C++ file. To fix the error you need to run the Visual C++ installation manually.
To run the Microsoft Visual C++ Redistibutable module:
If this does not resolve the problem please also run Windows Updates on your computer and install all important updates.
When running the program I get a "Could not load file or assembly" error.
Applies to: CodeManager 2008-2011
This error is caused because the Microsoft .NET Framework 2.0 is corrupted. Repairing the framework will fix the problem.
To repair the Microsoft .NET Framework 2.0:
I am installing or updating CodeManager 2008 or 2009. Either the installation gets to a certain
point and never progresses, or when I start the program the Updating AMA Products
dialog appears, gets to three bars, and never progresses.
Applies to: CodeManager 2008 Q2, Q3, Q4, 2009 Q1
This error occurs when the new update attempts to synchronize with older AMA programs, such as CPT Assistant Archives 1990-2005. In most cases where this error occurs multiple older versions of CodeManager and/or CPT Assistant Archives, and/or CPT Changes Archives are installed on the machine.
To repair this error you must update to a later version of CodeManager 2009 (Q2-Q4). Please install CodeManager 2009 Q4 from the CD. The CD will automatically update you to Q4, regardless of what previous version is on the machine.
When trying to install CodeManager I get an error while installing system components, or a message
that MDAC 2.8 won't install, or other error during the installation.
Applies to: CodeManager 2008, 2009
This type of error is usually caused by being on service pack 1 of the Windows XP operating system. CodeManager requires service pack 2 or later.
To update your operating system:
After completely updating your operating system the installation should run and install CodeManager normally.
When I try to access Medicare Rules I get an "Internal Server" error, or when I try to start the RBRVS Payment Calculator
I get an "Internal Server" error, or when I try to use notes nothing happens or I get an access error.
Applies to: CodeManager 2006, 2007
You can access the solution to this issue here.
When I try to fax in my registration I get a voice number.
Applies to: CodeManager 2005 Q1
Two numbers of the phone number given were inadvertently transposed. The correct number to fax in your registration is 312-464-5837.
I have both CodeManager 2005 and CPT Assistant Archives 1990-2003. I installed CodeManager, then CPT Assistant Archives. After the
installation the programs do not recognize each other as they should.
Applies to: CodeManager 2005 and CPT Assistant Archives 1990-2003
The documentation incorrectly states that the programs can be installed in any order. Since CPT Assistant Archives 1990-2003 was published before CodeManager it needs to be installed before CodeManager. Please install CPT Assistant Archives first, then CodeManager. CodeManager will then set up the interaction properly.
If you have already installed both programs and they are not working together you do not need to uninstall both of them. Just
uninstall CodeManager and reinstall it. Since CPT Assistant Archives will be on the computer when CodeManager is installed,
the interaction will be set up properly.
When I try to run the installation Windows cannot find Setup.exe or one of its
components.
Applies to: CodeManager installation program
Make sure you have specified the correct drive letter and path. The format should be
"d:\setup.exe", without the quotes where "d" is the letter of your CD
drive. Also double check that you have the correct CD and that it is placed in the drive
properly. If the CD is dirty, carefully clean it with a soft cloth. To help determine if
the problem is with the CD or with the drive you can try to read the CD in the drive of
another computer.
When I try to run the installation I get a message that says something about InstallShield not being able to initialize or that there was a catastrophic failure before the installation even starts.
Applies to: CodeManager installation program
These are issues with the InstallShield installation engine. To resolve the problem we suggest you first go to http://support.installshield.com/kb/view.asp?articleid=q104985. Start with suggestion 9 under "Professional 6.x Users" about installing Dcom98.exe, then start at the top and work your way down. Don't use the suggestions under "Professional 7.x" as they don't apply. If you have CodeManager 2005 or later, use the suggestions under DevStudio 9.x.
If you are still having a problem, move on to http://support.installshield.com/kb/view.asp?articleid=q104986 and follow the suggestions for your operating system.
If you need to install ikernal, you can use this link for instructions: http://consumer.installshield.com/kb.asp?id=Q108312.
When I try to install CodeManager everything proceeds fine until the installation tries
to update the registry. At this point the message “Updating the registry. This may
take several minutes” appears but does not go away.
Applies to: CodeManager installation program
One common cause of this problem is antivirus software. Antivirus software can prevent
the installation from making registry changes necessary to run CodeManager. Disable the antivirus software
and run the installation again.
When I try to install CodeManager everything proceeds fine until it gets to a certain point during the copy process, then the progress bar stops moving. It seems to hang.
Applies to: CodeManager installation program
CodeManager currently uses a large number of small files. While these files are copying the progress bar will slow significantly. The progress bar is not a good indicator of the actual progress of the installation.
To determine if your installation has hung, check the activity indicator of the hard drive to which you are installing. If the light is flashing, the installation is still working regardless of whether the progress bar is moving. Even if there is no activity on the hard drive, the installation may still be working. Wait at least a full hour. If, after that time, the progress bar has not moved and there has been no disk activity then click the “Cancel” button.
If the installation responds (give it a minute) by asking “Are you sure you want to cancel the setup?”, it may still be working. If you have the time, answer “No” and let it continue for a few more hours. If you don't have the time, or it has been several hours, answer “Yes”. If the installation responds with a lot of disk activity and then an “InstallShield Wizard Complete” dialog, you can attempt another installation after checking the amount of space on the destination hard drive and rebooting your computer.
If the installation does not respond to the Cancel command, then assume the installation has hung.
To stop the installation when it is not responding, go to the Windows Task Manager by typing Ctrl-Alt-Del. When the Task Manager appears, find "CodeManager 2005 - InstallShield Wizard" on the Applications list, click it once to select it, then click "End Task" and wait for Windows to close the installation and remove it from the list.
To remove CodeManager manually
After the installation has stopped you will need to remove the files it copied and any registry entries it may have made before it hung. To do this, use your Windows Explorer to find the installation directory (the default is “C:\Program Files\AMA\CodeManager 2005”) and delete the entire directory. CodeManager only puts files in this directory tree so all CodeManager files will be removed when you delete the directory.
To remove any registry entries the installation has made, open the Registry Editor by going to Start, Run, and typing “regedit” in the Open box, then clicking OK. In the Registry Editor, click the plus next to HKEY_LOCAL_MACHINE. Under HKEY_LOCAL_MACHINE, click the plus next to SOFTWARE. Under SOFTWARE, look for AMACM2005 (or other year). Right click on AMACM2005, then left click on Delete. Confirm the removal of the key by clicking Yes.
Now that you have undone whatever the installation did, check the space on the hard drive to which you will install, reboot your computer, and run the installation again.
I have installed CodeManager on my computer. The installation ran fine and gave no errors. However, when I double-click the CodeManager icon, the first window appears, then my browser appears, then I receive the error “The page cannot be displayed...”
Applies to: 2004 and later
There are two causes of this error. It could be caused by the settings in the browser, or by security software that is preventing the CodeManager server from communicating with the browser.
Check the settings first. With your Internet Explorer browser open, go to the Tools menu at the top, then to Internet Options. Click on the Content tab, then click on the LAN Settings button towards the bottom. On the “Local Area Network (LAN) Settings” dialog, check the “Use automatic configuration script” option in the “Automatic configuration” section. This will activate the Address box. Type “localhost” (without quotes) in the box.
Now look at the “Proxy server” section. If the “Use a proxy server for your LAN” box is checked, then you must also check the “Bypass proxy server for local addresses” box. If the proxy server box is not checked, you can leave the local address box blank as well.
Click OK to exit the dialog.
Next click on the Programs tab. Click the “Reset Web Settings...” button. Clear the “Also reset my home page” box, then click Yes. Click OK to acknowledge that the settings have been reset.
Click OK on the Internet Options dialog, close the browser, close the CodeManager dialog, then restart CodeManager. If you still get the error, then you have security software that is preventing the CodeManager server from communication with the browser.
Any internet security software could be interferring with CodeManager. You will need to refer to the documentation that came with the security software to configure it so CodeManager can communicate on port 8780 with your browser. Note in Windows XP SP2 you must also add the program (cd_run.exe) that starts CodeManager.
I have updated a previous version of CodeManager with a new quarterly update, however, after the update CodeManager does not function properly. The updated information works but the previous information is not working.
Applies to: 2004 and later
The most likely cause of this issue is skipping a quarter. You cannot update from Q2 to Q4 for example. The Q4 update must be run on the Q3 version to function properly.
If you have skipped a quarter, uninstall CodeManager and rerun the installation. If the installation still says it is updating an existing version of CodeManager, follow the instructions above for removing it manually, then run the installation again.
I have installed CodeManager on my computer. The installation ran fine and gave no errors. However, when I try to click on a code number to get further information, nothing happens.
Applies to: 2004 and later
CodeManager uses popup windows in many places to show options for a code. If you have popup-blocking software running, it can prevent these windows from showing. Turn off the popup-blocking software while using CodeManager.
CodeManager 2004 or later does not interact with CPT Assistant Archives 1990-2002 or earlier
Applies to: 2004 and later
CPT Assistant Archives 1990-2002, published in 2003, was based on the Folio platform. CodeManager 2004 uses a browser-based platform that does not interact with Folio. Therefore, the two programs must be run separately.
(Last updated 2009-02-04)
© 2012 American Medical Association. All Rights Reserved.
CPT © 2011 American Medical Association. CPT and CodeManager are registered trademarks of the American Medical Association.