Receive Error in NWSMSCRN for Function Pf-Map-Coordinate-Space

Receive Error in NWSMSCRN for Function Pf-Map-Coordinate-Space

Q - In Elliott, I receive the following error from time to time:
Error in NWSMSCRN

Function:
   0000 Pf-Map-Coordinate-Space
Status:
   00000 yyyyyyyyyyyyyyyyyyyyyyyyyyyyy



If you click on the OK button, you can continue to do what you need to do.  This is somewhat annoying.  What causes this to happen?

A - From what we have seen in the past, the type of font you choose may cause this to happen.  With the past three incidents, one user was using the following font in Elliott V7.5:

15x30 MS Gothic

the second user was using the following font in Elliott V7.5:

17x33 MS Gothic-Bold

In the other incident, the user was using the following font in Elliott V7.5:

           16x25 Lucida Console - Bold

After the users changed to a different font, the problem went away.  The exact reason for this error is still unknown.

EMK




    • Related Articles

    • Elliott Synchronizing to Local Error - There is not enough space on the disk

      Release Date: 05/04/2022 Version: 8.5 & Higher Q - We just had an Elliott update last night. Now some of our users are getting this error today. It is not all users and not even all users on specific remote desktop servers. Even after restarting & ...

    • Btrieve Error Codes 001 - 199

      MicroKernel (Btrieve) Database Engine Status Codes This section describes status codes that the MicroKernel returns. All status codes are provided in 3-digit formats since the search on this website cannot search 1 or 2-digit words correctly. That is ...

    • Btrieve Error Codes 3000 - 3099

      MicroKernel Router Status Codes This section lists the status codes you can receive from the MicroKernel router, which receives requests from the Btrieve requesters and routes them to the correct version of the MicroKernel. 3000: The MicroKernel ...

    • Btrieve Error Codes 3100 - 3199

      Network Services Layer Status Codes The following status codes originate from the Pervasive Network Services Layer (PNSL). 3103: Server name not found by Pervasive Network Services Layer The search for a target server name was unable to resolve an ...

    • Btrieve Error USE on COP Lock File

      Q - Today, for whatever reason, we experienced a large amount of locking issues in the warehouse. Several times today we ran into the problem with printing invoices where we received a message "Btrieve Error USE on COP Lock File," and it stops ...