Answers in this category:
Message; "op_prt_buf, print new page fa".
Message; “free_pool() - attempting to free unallocated memory ()”
Message; “Internal Error has Occurred, Proceed with Caution”
Message; "Cannot write any more qdaemon"
Message "memcpy - trash the heap"
Message; "unknown AppxIO status"
Message; "Can't connect to host"
Message; “PDF_begin_page: Function must not be called in ‘page’ scope”
Message; “Connection Refused by Host”
Message; “Application Lock verification failed. Access Denied”.
Message; “can't write cwdgt - Error - Already on File”
Message; “Cannot read cfi_rec”
Message: “mm_free() 'freeing watched address' or 'attempting to free freed memory'"
Message; "pl rloc - too few cchld records(1)"
Message; “ID not defined as valid Login”
Message; “File Organization Specification Mismatch”
Message; “License Server not Detected”
Message; "file does not exist"
Message; "Can't connect to Host" or "Connection refused by host" (Troubleshooting WinAppxD)
Message; "Allocation of TOKEN_USER failed"
Message; "LookupAccountSid() failed"
Message; "can't open stream socket"
Message; "can't bind local address"
Message; "op_prt_buf, print new page failed"
Message; “There was an error opening this document. No such file or directory”
NET_LOG 'error's 122 & 10054
PDF Output: "Windows cannot find $display"
Message: "required data was not placed into memory because of an I/O error"
Message – “Error - Invalid Request Using Main ARB”
Message "Found active record on freelist"
Message. "ERROR - CANNOT ACCESS REQUIRED FILE"
What does error "Can't read LFN File - Error - Already on File" mean?
Message, "can't empty sarb list"
Message, "bad reg no."
Message "An unexpected error occurred, please enable logging and retry"
Message "Cannot write to Cache - Invalid Prototype Record Length"
Message; "No Record Currently Held"
Message, Error - Request Not Allowed
Message, "BI.C - APPX Startup Failure: Unable to Initialize Window Manager"
Message: "key field conversion failure - Error - Invalid Logical Value"
Message; "too much data"
Message, "Network IO Error"
Message, "ORA-01000: maximum open cursors exceeded"

If you can reproduce the error, we'd love to get a copy of the replication, so we can fix it. Frequently the error is not easily reproducible, so any scenario we can get that reproduces it would be helpful.

       "Enq: (FATAL ERROR): 0781-024 Cannot write anymore to
       /var/spool/qdaemon/to4mZM"

The /var file system is full. Delete some unneeded files out of the file system.

This error occurs when a page break triggers another page break. For example, setting "new page before" on a page heading frame. Refer to bugtracker bug #517 and #617

1. winappxd/appxdsvc (listener) is not running on the server (host)
2. the port you entered is not valid for the listener(s) you have running
3. the workstation is not connected to the server where the listener is running

Referring to item 3 above. If you are entering a server name and you are sure the listener is running and the port is correct, try entering the ip address of the server instead. If you connect, most likely your DNS name is not mapped to the right ip address. You will have to resolve your DNS server mapping to eliminate this error.

This error occurs when Appx takes the snapshot (after you've had a chance to change the widgets with ILF code).

The primary key to the internal widget file is position row+position col. There's an alternate unique key that on name + appearance number. Check for duplicate name+appearance number.

PL.C.2842 - "Cannot read cfi rec - Error - Record Not in File",

followed by "Internal Error Has Been Detected, proceed with caution!".

To diagnose these, set the two environment variables:

        APPX_TRAILER_COUNT=40

        APPX_LABEL_MEMORY=1

When then running into the above error messages, send a copy of the error message itself (a screen snapshot if possible) to Appx technical support.

On Windows platforms, also send a copy of the 'appx.stk' file found in the same directory as the Appx engine. (It may then be safely deleted.)

Consider also performing the cleanup steps described in: http://www.appx.com/assets/asp/dynamic_generator.asp?pageid=584

It did let him enter an OS login of "RND/abc". But when he then logged into his OS as RND/abc, then into Appx, it told him - "Bad User Id - The User Id you are currently using was not found in the APPX user file."

VAR deleted .\data\0SA\Data\USER.* in order to be able to enter Appx. In Security > Users he tried entering "abc", but it gave him the "not currently defined" message. It did let him enter an OS Login ID of "RND/abc", but again wouldn't let "abc" log in.

VAR didn't notice that there was the word "Warning" in front of the first message. Because of confusion of local IDs and domain ID, Appx validates against the domain id, but allows entry of only the user portion of the Domain/User ID.

I.E., "abc" works for logging in, but generates a Warning during OS Login ID Entry. "RND/abc" doesn't work for logging in, but generates no warning during OS Login ID entry.

If you're in a Domain environment, enter only the user part of the user's OS Login ID. Also, ignore the "Warning - This ID is not currently defined..." message.

Note, this message was changed from 'Error' to 'Warning' in 4.1.8. If your Appx version is prior to 4.1.8, it's probably necessary to upgrade to 4.1.8 or higher in order to be able to enter OS Login ID’s.

You can also get this error if a file is damaged. If a {file}.dat is damaged and you rebuild the {file}.key from it, you may or may not get an error message indicating that there's a problem in the .dat. If you get no message, you could be left with the impression that your .dat/.key pair are good. Running verify may or may not tell you if there's a problem. (This is a low probability, but possible scenario.)

Your safest course of action is to run through the "What to do with a file That Fails Verification" procedure in

http://www.appx.com/assets/asp/dynamic_generator.asp?pageid=624

You can do a bit more investigation using the techniques in "Verifying and Analyzing a File" on that webpage. Using the utility program Recover.exe is the recommended course of action. Exporting and re-importing the file will work however may result in more lost data. The Export program will only read to the "bad spot" on the file and stop whereas Recover.exe will continue to the end of file reading and writing records beyond the error. Information on this utility can be found at the above address.

 appx -l=logfile

Consider deleting the data\0SA\Data\USAGE.*, .\REGISTER.dat, and .\LOCK.* files, then re-import the registration.

For an NT based Presentation Server (WinAppxD), see the FAQ “Service is not running” for debugging approaches. Also for NT Presentation Server:

1) Bring up the Task Manager and look for a WinAppxD process, which should tell us whether WinAppxD is running.

2) Running "netstat -a" and looking for "*.8060" (for example) in the "Local Address" list will tell you if anything is listening on the port. For example:

C:\WINDOWS> netstat -a Active Connections Proto Local Address Foreign Address State TCP oz:1079 P66:0 LISTENING TCP oz:1650 P66:0 LISTENING TCP oz:1656 P66:0 LISTENING TCP oz:1533 P66:0 LISTENING Services for WinAppxD has a radio button giving alternatives for 'System' or 'This Account:'. The latter should be on, with UserID equal to the APPX user set up for this Presentation Server. Try reentering the password for this User Account. Then Re-IPL.

For a Unix based Presentation Server:

To see what Presentation Servers are running, execute: ps -ef | grep appxd To see what ports (prefixed with '806') are being listened to: netstat -a | grep 806 Proto Recv-Q Send-Q Local Address Foreign Address (state) tcp 0 0 *.8064 *.* LISTEN tcp 0 0 *.8068 *.* LISTEN tcp 0 0 *.8067 *.* LISTEN.

Reboot and try again. If it still fails, call APPX Software Technical Support.

Resolution: Reboot and try again. If it still fails, call APPX Software Technical Support.

1. A lingering copy of WinAppxD. Check to make sure no copies of WinAppxD are listed in Task Manager. This may occur if you Start and Stop the WinAppxD service using Control Panel, or if you run WinAppxD from the command line during troubleshooting. If you see any rogue WinAppxD's, kill them and try again.

2. Some other (non-APPX) application wants to use the port you specified in the "-s=" argument for WinAppxD during installation. There is no completely reliable way to detect this. If you are getting the "can't bind" error and are sure it's not due to an extra WinAppxD process running, this is probably what has happened. Since WinAppxD can't use a port claimed by another application, go back and edit the registry, choosing a different port number for the WinAppxD service. For example, try 8061 instead of 8060. Reboot, and try again.

In the course of Appx/Clients attaching to a WinAppxD Appx/Server, with 
APPX NET_LOG enabled, the following NET LOG entries can come up.  Here are 
explanations:

        SetProcessWindowStation() returned 1, (err=122)
        CreateDesktop() returned 168 (err=122)

 These aren't errors.  They would be errors if they had returned 0.

        recv() failed, exiting, errno = 10054

 "An existing connection was forcibly closed by the remote host."
                                        (From the MS Win32 API Error Codes)

This can be caused by something in the network (aka an 'assassin') sending a 
RESET packet.  This kills WinAppxD, and therefore all links between 
Appx/Clients and the Appx/Server.  The Appx/Server may or may not be able to 
manually restart, depending on whether something in the network is holding the 
old port open or not.  If the port is being held open, the Appx/Server can't 
grab it again.

That "something in the network" could be routers, modems, or other equipment 
in the network.

                 $display:         (can look like "Sdisplay")

 Windows cannot find '$display:'. Make sure you typed the
 name correctly, and then try again. To search for a file,
 click the Start button, and then click Search.

                    OK

     Appx - 41440:  appx.exe - application error

  The instruction at 0x004992b0 referenced memory at 0x004992b0.   
  The required data was not placed into memory because of an 
  I/O error status of 0xc000020c.

There were most likely occasional, brief network problems when trying to load a block of appx.exe executable into his client PC. This can happen after initial appx.exe -c program loading, because the OS grabs 2k blocks of the disk form of the executable, as needed. (The problem can also be a disk fark, or a controller error.)

The solution is to bring the appx.exe previously stored on the network server down to the local PC hard drive, to eliminate this potential network problem.

This error can also happen when a temporary file is created in a process and that temporary file is not deleted completely. Under normal conditions, APPX will delete temporary files (Disk Related for example), when the process ends. Look for the presents a .key components without a corresponding .dat for the file in your database directory for the offending application. Delete the .key file manually if necessary.

'sarb' is an abbreviation for 'slave arb'. A sarb is a slave to a 'marb' (a master arb). An 'arb' is an access request block - it's the internal representation of a file stream. When you OPEN a file, you get a new arb. Appx creates arbs for you when you BEG/END READ, or when you invoke a new process.

Recommended course of action, determine what process was running then look at the file(s) that were open. Check the number of alternate keys. Appx allows for 1 primary and 15 alternate keys. If you exceed this you could get this error. You should also delete the em(s) and run the process again.

You may see this message from Subroutine CSE. CSE is the Call Statement Editor.

* It tries in 4 different places to open the USAGE file and if it fails it sets this flag.
* Tries to lock some kind of sentinal record, a failure sets this flag.
* If it fails to read a USAGE record in 2 cases it sets this flag.
* If it fails to writed to the USAGE file it sets this flag.

The basic problem might be a corrupt USAGE file.
That message means exactly what it says - enable logging and retry (then, of course, check the log).
The license server always produces a minimal log file (the file name displays when the license server starts or you can appx -l=filename). To turn up the logging level, set APPX_LS_DBG=0xFFFFFFFF
The easiest fix would be to delete the USAGE file. If that doesn't work, we need the log.

APPX can maintain three threads to the same file; one for the PCF, one for READ/READNEXT and one for BEG READ/END READ loops. When you READ the PCF in ILF (sub-process level), it resets the hold pointer depending on the READ specifications. That’s why the STORE, READ with hold, and RESTORE in Pre-PCF Update works. It re-established the hold on the record APPX automatically read from the PCF. Of course the interactive phase is import too. Appx won’t hold the record in Inquire mode for example. Also keep in mind that the data record is also stored in the common area and subsequent READ statements may replace the record read (and perhaps displayed) from the PCF. It can be a slippery-slop when you start messing around with the PCF in your application. There are certainly situations where it’s necessary but it could be done accidentally as well.

A record will be released by the REWRITE, DELETE, or CLOSE statements. Why, Appx assumes when you execute any of these commands you are done with the record.

As mentioned above, a READ or READNEXT creates a second thread into the file but uses the same common area as the parent. So if you access the PCF in ILF with hold, the hold pointer and record buffer are changed in the common area. When you return to your input screen after the events points, or sub-process child have executed APPX expects the PCF record to be held (in change mode). Since you re-established the hold in ILF, the hold at the PCF level has been lost. This might be what is happening in your case. That’s what the message is in the status line (in red) is telling you. If you tried to REWRITE or DELETE a record in ILF and didn’t have the hold, Appx would display the ILF code that was causing the problem.

You can also release the hold by invoking a sub-process child that uses the same PCF as the parent. Sub-process children share the common area with the parent. Basically the same thing happens as a READ, but APPX has read the file and may have reset the hold. This would happen on an input process invoked as a sub-process that has the same PCF as the parent.

You should analyze your system to determine where the hold is being released. We can’t tell you specifically where to look because, as described above, the hold can be release in any number of ways depending how your system is coded. If this just started happening, I would find out what has recently changed and investigate what the programmer may have done that resulted in this situation.

Perhaps something is being changed in the data dictionary that alters the length of the current buffer and Appx maybe has a copy of the data stuck is a save buffer that it is trying to restore.

Most of the time this error is the result of lack of permissions on the Appx directory. Appx users must have full control within the Appx directory and all sub-folders within it. They also need to be able to run the Appx executable on the server with logon local rights.

We have seen this error caused by a spam filter. If any new spam/virus filters been added to your server in the past few months, could you turn them off briefly to test connectivity?

You might get this error if you're running a newer version of the client than the engine. Example, running Appx 4.2.a with the 5.0.1 client.

It has been found that exiting a BEG READ/END READ loop that is accessing an Oracle table will not close cursors properly. In this case you should write your Appx ILF process to always execute the END READ statement for each READ.

Tuning OPEN_CURSORS

The best advice for tuning OPEN_CURSORS is not to tune it. Set it high enough that you won't have to worry about it. If your sessions are running close to the limit you've set for OPEN_CURSORS, raise it. Your goal in tuning this parameter is to set it high enough that you never get an error during normal operations.

If you set OPEN_CURSORS to a high value, this doesn't mean that every session will have that number of cursors open. Cursors are opened on an as-needed basis. And if one of your applications has a cursor leak, it will eventually show up even with OPEN_CURSORS set high. Your DBA should be able to monitor the number of open cursors.

After you've increased the value of OPEN_CURSORS, continue monitoring to see if opened cursors keeps increasing for any of your sessions. If you have an application session whose opened cursors always increases, then you've likely got a cursor leak in your application code: your application is opening cursors and not closing them when it's done.

There is nothing you (DBA), can do to fix a cursor leak. The application developers need to go through the code, find the cursors that are being left open, and close them. As a stopgap, the most you can do is raise OPEN_CURSORS very high and schedule times when all the application sessions will be closed and reopened.

How not to tell if you're closing all your cursors

Frustratingly for developers, the session statistic 'currently open cursors' can include some cursors that the application has closed. When application code calls for a cursor to be closed, Oracle actually marks the cursor as "closeable". The cursor may not actually be closed until Oracle needs the space for another cursor.

So it's not possible to test to see if a complex application is closing all its cursors by starting a session, running a test, and then checking to see if currently open cursors has gone down to 1. Even if the application is closing all its cursors properly, currently open cursors may report that some "closeable" cursors are still open.

One way for application developers to tell if an application is closing all its cursors is to do a single test run, on a dedicated development box, while monitoring opened cursors for the session that's running the test. Then set OPEN_CURSORS to a value a little bit higher than the peak cursors open during your test run, start a new session, and run through multiple iterations of the same test run. If your application still has a cursor leak, you will see the value of OPEN_CURSORS going up, and you may hit an ORA-1000 after a reasonable number of iterations. (Don't set OPEN_CURSORS too low or it may be used up by recursive SQL; if your single test run opens very few cursors, consider making your test run longer rather than setting OPEN_CURSORS unreasonably low.)