Norman problems and solutions
The most common problems, and solutions, regarding Norman are discussed here. When you have a problem, with or without solution, post it on the forum or email it to the webmaster. Your suggestion will be reviewed and added.
Problem: After updating the following error appears 'This program has performed an illegal operation and will be shut down. If the problem persists, contact the program vendor.'
Solution:
Download and install the fix below for your language to solve the problem.
The All languages download is a larger download containing all supported language versions.
After you have installed the fix, wait a few minutes while the update completes its installation.
Then you must restart your computer for the new module to take effect.
- Chinese (simplified)
- Chinese (traditional)
- Czech
- Danish
- Dutch
- English
- Finnish
- French
- German
- Italian
- Norwegian
- Polish
- Portuguese
- Slovenian
- Spanish
- Swedish
- All languages
Problem: Using NVC 5.7 the updates will not complete or the updating process will enter a loop
Solution:
- Double-click the clock in your system tray or select Date and Time from the Control panel in Windows
- Revert the date to any date before 05 August 2005
- Wait for the installation/update to complete. Restart the computer if the installation promts you to
- Click the N system tray icon and select Internet Update to make sure that your installation is up-to-date
- If updates are downloaded, wait a few minutes while they are installed and restart your computer if the installation prompts you to
- Reset correct date settings
If you for some reason cannot modify the date on your computer, download and install ZanUpdFix.exe and restart your computer when prompted to do so
Problem: Elogger is reporting missing norman.ndf
Solution:This does not indicate that something is wrong. Norman.ndf will be
introduced later as a part of our new license system. For now, you can
safely ignore messages related to this file in Elogger.
Problem: Red cross on machines in NDesk
Solution:
When enumerating the network with NDesk, a lot of NT4/2000/XP machines on the Installations tab appear with a red cross indicating that NVC is not and cannot be installed.
NDesk will only work as a distribution tool for Windows NT4, 2000 and XP machines that have:
- Ping enabled
- File/print sharing enabled
- Default shares for administrative use (e.g. IPC$ C$)
In addition the user running NDesk must have Domain Admin or equivalent privileges and "Reply to broadcasts and enable message routing of:" option must be enabled in the Message routing module of the NVC configuration.
When distributing NVC to XP machines in workgroups, the target machine must have disabled simple file sharing. You can do this from Windows Explorer or My computer:
- Select Folder options from the Tools menu
- Click on the tab View and unselect Use simple file sharing
You must reboot the target machine for this change to take effect
Problem 2: Windows 95 only)
One may also get a red cross on the Windows 95 machines where NVC is supposed to be installed already.
System requirements for NVC to run successfully on Windows 95 are Windows Socket 2 and Internet Explorer 4.0 or higher. If Winsock2 is not installed, the machine will not be able to return the correct status to Ndesk.
Problem: Error decompressing install file (ndesk)
Solution: This error will occur when trying to distribute a new version of NVC with an old version of NDesk. Download and install the Administration tools for the latest version of NVC to fix the problem.
Problem: Invalid server share (ndesk)
Solution: This error will occur if the path you have submitted in the Distribution source field does not exist, or if you have not shared the distribution source folder and applied sufficient permissions.
Problem: An undefined error has occured (ndesk)
Solution: This error may have several explanations:
- You may only use NDesk for push-based distribution to computers running Windows NT4/2000/XP/2003. However, you may also monitor and operate installations on Windows 95/98/Me, where the initial distribution is done through the SelfxWiz installation tool. These installations will appear on NDesk’s Installations tab just as the others, but you will get the error message above if you select Install Zanda from the right-click menu and check the Overwrite existing installations option.
- The user running NDesk cannot access the remote target machine’s registry (...\Software\Microsoft\Windows NT\CurrentVersion)
- You have checked the "overwrite existing" checkbox, but removing the existing Zanda service fails for some reason. This is always accompanied by a Norman error dialog.
Problem: The specified user cannot be used by Zanda to fetch files from the distribution server. Please check for typing errors and or the user credentials on the distribution server Solution: This error message will appear if you have misspelled or used incorrect syntax for account or password in NDesk's Install Zanda dialogue. When this problem occurs, you should check that the information is correct both in your Default.ndf configuration file's LAN/WAN tab and in the Install Zanda dialogue before moving on with the installation.
Problem: The procedure entry point_NvcOemGetResourceIds@4 could not be located in the dynamic link library noemrc.dll
Solution: Earlier versions of the Administration tools are not compatible with NVC v5.8. After upgrading NVC to version 5.8, you must therefore download and install the latest Administration tools available.
Note that the Administration tools as off NVC v5.8 are residing within the ...\Norman\Bin folder, and not in ...\Norman\Nvc\Bin as in previous versions.
Problem: Norman Program Manager could not complete the installation or update due to an unexpected error. Please save your work and then click the ’Restart now’ button
Solution:
We have seen this problem in installations where an old version of Norman software has been installed on computers that are already running a later version. In such scenario we recommend that you reinstall NVC/NIC according to the procedure on one of the following links:
...if an update failsDuring an upgrade Norman Program Manager’s (Zanda) task is to upgrade itself and/or several other Norman modules.
From time to time this complex operation fails:
- If lots of software starts during boot time of the computer, we have seen that timeouts have occurred
- If zip files in the ...\Norman\Download folder are corrupted
- If there is not sufficient disk space for the upgrade
In single user installations the recommended solution is to reinstall the Norman program according to the procedure described on the links above.
In networks the following steps may resolve the situation
- Delete all files from the folder ...\Norman\Download on the affected client(s)
- Delete all *.tmp files from the folders ...\Norman\Bin and ...\Norman\Nvc\Bin on computers that have the problem
- Copy all zip files from ...\Distrib\Download\ to ...\Norman\Download.
- Run NDesk, select Install Zanda and “Overwrite existing installation" for the installation(s) in question.
OR
Copy Delnvc5 from ...\Norman\Nvc\Bin on an up-to-date and running installation and run it on the affected installation(s). If you run Delnvc5 manually, select Repair. You may also run Delnvc5 /repair from a script.
If NVC is distributed in the network by using SelfXWiz (Nvc5W32), running the installation package with /ow (“nvc5w32.exe /ow") may also solve the problem.
Problem: After changing my Internet connection type from dial-up connection
(modem) to a broadband (xDSL) connection, NVC is not updated anymore.
Internet Update pops-up a dialog telling that NIU is waiting for
connection.
Solution:
- Open the Configuration Editor
- Go to the tab Internet in the Install and update products section
- Make sure that your selection in the section for When to look for updates on the Internet corresponds with your type of Internet connection.
Problem: Unexpected error returned from library:
Context: LoadNiuState
Routine: NiuStateRead
Error value: 0x00110004
Error code: NDFRC_FILE_DAMAGED
Solution: This is caused by a corrupt file in your NVC installation. Delete the file c:\norman\nvc\config\niustate.ndf to remedy the problem. A new niustate.ndf will be created the next time you run Norman Internet Update.
Problem: Configuration error: Requested component files are either nonexisting or inconsistent with your authentication key
Solution: When running Norman Internet Update, I get the following error message:
"Configuration error: Requested component files are either nonexisting or inconsistent with your authentication key."
This means that you are trying to update a Norman product on a platform that you are not licensed for, or that your authentication key contains wrong license data. The error will for example occur if you try to update a server, and your authentication key covers workstations only.
Problem: After installing/upgrading to NVC v 5.7 neither drag and drop nor paste
work anymore from the graphical user interface in Windows 95. However,
the copy command still works from command prompt.
Solution:
- Open the Configuration Editor
- Unselect Internet Protection from the tab Start
- Save
- Reboot the computer
Problem: Problems running Scandisk and Defrag
Solution: Download and run this tool (Ndefrag) for Windows 95/98/Me to work around the problem.
Here is what Ndefrag will do:
- Warn you that your PC will remain unprotected while scandisk/defrag is running
- Prompt you to run scandisk or defrag
- Automatically start NVC again when the operation is completed
Problem: Error code 0x80070725 - "Incompatible Version of the RPC Stub"
Solution: Details of the error, and how to correct it can be found in the Microsoft Knowledgebase: http://support.microsoft.com/default.aspx?scid=kb;en-us;q321915 and the InstallShield Knowledgebase: http://support.installshield.com/kb/view.asp?pcode=ALL&articleid=Q105810
Problem: Error message "Access to data denied" when opening Lotus Notes mail or documents
Solution: This error may occur if you have enabled "Scan new or changed files" in the configuration for On-access scanner (Local users). Disable this option to solve the problem.
- Open the Configuration Editor
- Select On-access scanner (Local users) from the Norman Virus Control configuration branch
- Unselect "Scan new or changed files"
- Save
Problem: Application crash problems after installation/upgrade of NVC
Solution: Norman Virus Control is thoroughly tested on all supported operating system platforms and with a lot of third party software before new versions are released. Still, we will never be able to cover all applications and scenarios through this testing, and crashes may occur.
In general, you should never have to go as far as uninstalling Norman Virus Control to get things to work. Very often a conflict that causes third party applications to crash is related to real-time scanning components like On-access scanner and Internet Protection (NIP). To locate the problem you should stop these components one-by-one
Stop Internet Protection
- Open the Configuration Editor (single user installations) or Default.ndf (network installations) and unselect Internet protection from the tab Start in the Norman Virus Control configuration branch.
- Save
You may have to close and restart the affected application or even reboot your computer before the change will take effect.
NOTE: Deactivating Internet Protection does NOT leave your PC without virus protection. Viruses received via mail or Usenet will still be stopped by the on-access scanner.
If stopping Internet Protection has no effect and your application still crashes, the next step should be to stop the On-access scanner. Before you do this you should reverse the above-mentioned procedure, to make sure that only one parameter at the time is changed.
Stop On-access scanner
- Select Stop On-access scanner from the N-icon tray menu (single user installations) or unselect On-access scanner from the tab Start in Default.ndf (network installations).
- Save (network installations)
If your problem is related to Norman Virus Control, you have probably identified the conflict by now. Stopping NVC components should only be a temporary solution, and Norman needs information on how to reproduce the problem when crash situations occur.
Problem: Error messages from CCLAW, NVCOA, NVCOD, ZANDA or ZLH after installation/update
Solution: Run the file Delnvc5.exe from the folder ...\Norman\Nvc\Bin and select Repair. This will force the program manager to reinstall the software.
To do this in a network you may run Delnvc5 /repair from a script.
The Repair option will probably solve your problem. If so is not the case, check that the machine with the error message meets the system requirements for NVC. If not, install the necessary updates, run Delnvc5, choose Remove, and reboot before you reinstall NVC.
Problem: Nfshook.dll was not found
Solution: Download Delnvc5 from this link, run the program and select Repair. Your installation will be OK after a few minutes.
Problem: ”Cannot parse or unpack this object” when scanning JAR files with On-demand scanner
Solution: Download and install Exp190905 to solve the problem. Wait a few minutes while the Program manager completes the update in the background before scanning the affected files again.
Problem: Access denied when running Internet Update (NIU) from the tray icon menu
Solution: When you select Internet Update from the system tray icon (N), it is running on the local system account, which does not necessarily have the same user rights (credentials) on the network as the currently logged in user. This is due to the architecture of Windows NT.
Regardless of this, you should be able to run NIU from Start | Programs | Norman Virus Control | Internet Update.
Problem: High memory usage and/or CPU load from NVCOAS
Solution: This problem may be due to a faulty configuration of the On-access scanner. Recommended strategy for On-access scanner (non interactive) is "Scan new or changed files".
Selecting "Scan files before they are used" may increase the load dramatically on servers. You should therefore not select this option unless you have a fast spreading virus infection in your network.
Problem: The computer automatically reboots (blue screen) when accessing network drives
Solution: This problem may occur in connection with a certain Windows 2000/XP/2003 operating system specific error, that the On-access scanner drivers in Norman Virus Control don’t handle correctly. We have also seen this error on Exchange installations.
The blue screen contains the following string and refers to nvcoaft5.sys or nvcoaft51.sys
PAGE_FAULT_IN_NONPAGED_AREA
Download this patch if you encounter this kind of crash situation with Norman Virus Control on Windows NT/2000/XP/2003.
Running the executable will install the appropriate drivers.
After a while NVC will ask you to reboot your system. Rebooting will complete the installation.
Problem: On-access scanner conflicting with Rapid Restore from IBM. After installing NVC on my IBM computer where also Rapid Restore is installed, the computer restarts automatically or crashes with a bluescreen.
MULTIPLE_IRP_COMPLETE_REQUESTS
*** STOP: 0x00000044 (0x81D18008, 0x00001B90, 0x00000000, 0x00000000)
Dumping physical memory
Solution: A patch for this problem was published through Internet Update (NIU)
2005.01.17. This patch is included in NVC v5.8 and later and will be
installed automatically when you run NIU.
Problem: Error message from cclaw.exe during boot. Module: cclaw.exe
Location CClaw.c(427)
Time: Tue May 13 11:40:43 2003
Error text: NPIPERC_TIMEOUT
Solution: A patch for this problem was published through Internet Update (NIU)
2005.01.17. This patch is included in NVC v5.8 and later and will be
installed automatically when you run NIU.
Problem: Computer blue-screening (BSOD) when USB flash-disk is inserted and NVC On-Access is active
Solution: Do you have Symantec Ghost installed? This is most likely a problem
with a Symantec Ghost driver (GhMon.sys). You need to update the Ghost
driver to solve the problem.
You can read more about the problem and download the updated driver here:
http://service1.symantec.com/SUPPORT/ghost.nsf/
d87bb6ce0bde286d88256d6a00452701/46596fbcc1df097c80256ed100392df7?
OpenDocument&src=bar_sch_nam
Source: Norman