Troubleshooting

Wikis > Package Manager > Troubleshooting

Startup errors

Startup errors are usually caused by conflicts with dlls of other applications which may be out of date or incompatible with the versions used in Arca Noae Package Manager. An example of this would be another application which utilizes VROBJEX.DLL, such as EVFSGUI through (at least) version 2.5RC7. When EVFSGUI is open, attempting to start Arca Noae Package Manager will result in an error message:

Cannot load window: Could not find class 'VRToolTip'

Check for other dlls in LIBPATH with the same names as those in the Arca Noae Package Manager installation directory.

First run errors

For systems with existing Python installations, please see this page.

On systems with no existing RPM & YUM installation, Arca Noae Package Manager should prompt to download and install the base package upon first program start. In certain instances, it is possible for the initial download of the base package to fail with:

The command terminated with error code 1.

This usually indicates that the TCP/IP stack is not 32-bit. Please upgrade the TCP/IP stack to 32-bit and re-try the operation.

YUM errors

A YUM error may cause the ANPM main window to be completely blank. A basic failure of this type may be encountered when symbolic links (symlinks) are unavailable on the system or on the volume designated as %UNIXROOT%. Because YUM depends upon Python, and because Python depends upon modules which are referenced through symlinks, these modules cannot be found and thus, YUM fails to start, leaving ANPM without input to display.

Running YUM from the command line, this condition may be seen more clearly:

There was a problem importing one of the Python modules 
required to run yum. The error leading to the problem was:

   dlopen rc=193 extra=X:\USR\LIB\PYTHON2.7\LIB-DYNLOAD\CSTRINGIO.PYD

Please install a package which provides this module, or 
verify that the module is installed correctly.

(X: is a placeholder for the volume designated as %UNIXROOT%.)

This indicates a failure of YUM to resolve a symlinked file pointing to a required module.

See the Netlabs RPM and YUM project page for more assistance.

YUM metadata and cache

These tasks are available from the Manage | YUM tools | Cleanup menu in Arca Noae Package Manager. See the Netlabs RPM and YUM project page for additional assistance.

Completing transactions

Sometimes, operations fail before completing, leaving the installation and the databases in varying states of inconsistency. This task is available from the Manage | YUM tools | Cleanup menu in Arca Noae Package Manager. See the Netlabs RPM and YUM project page for additional assistance.

RPM errors

See the Netlabs RPM and YUM project page for assistance.

Rebuild RPM database

This task is available from the Manage | YUM tools | Maintenance menu in Arca Noae Package Manager. See the Netlabs RPM and YUM project page for additional assistance.

Submitting Tickets

Before submitting a ticket, make sure you have read the main wiki page.

Reporting bugs and requesting new features is done through the ticketing system. You may view existing tickets, add comments, and create new tickets using the corresponding buttons at the top of every page. If you want to submit a new bug or request a feature, please use the Search function first to make sure there is no ticket for the same problem or feature request already created.