Troubleshooting

My APAServer is installed on Windows 2003 Server and when I try to connect the APAConsole to it a “The server process could not be started because the configured identity is incorrect. Check the username and password” message appear.
This problem occurs because the default identity for the application is set as Interactive User. Interactive user refers to the user that is logged on directly to the server console. If no interactive user exists, the application fails when it tries to assume the interactive user's identity.
To resolve this problem, change the identity for the server application to run under a particular user. To do this, on the Identity tab of the Application Properties dialog box, click This User. In addition, if it is feasible, you can ensure that a user is interactively logged on to the server console while the application is running.
In Microsoft Windows Server 2003, work around this problem by using the /Console switch to log on to Console/. To do this, follow these steps:
1. Click Start, click Run, type mstsc /console, and then click OK.
2. Log on to the computer.
Steps to Reproduce Behavior:
1. Create a new, empty COM+ Server application. Accept the default settings.
2. Add any component to the application. The component must not already be in another COM+ application.
3. Try to start the application remotely when no user is interactively logged on to the server console.

My APA Server is installed on a computer running Windows XP with Service Pack2. When APAConsole is attempting to connect to APA Server, “The RPC server is unavailable” appear.
Just do all of the sections in the order given and we hope the warning
Section 1: To ensure that the Windows Firewall is enabled
1. At the APAServer computer, log on as a user with Administrative privileges.
2. From the Start menu, click Settings > Control Panel.
3. If using the Classic View, double-click Windows Firewall. Otherwise, click Security Center and then, in the "Manage security settings for:" section, click Windows Firewall.
4. Select On (recommended).
Section 2: To enable Remote Administration traffic through the Firewall by enabling RPC and DCOM
1. From the Start menu, select All Programs > Accessories > Command
Prompt.
2. Type netsh
3. Type firewall
4. If the host and client are on the same subnet, type:
set service REMOTEADMIN ENABLE SUBNET
otherwise, type:
set service REMOTEADMIN ENABLE ALL
5. Type show service and verify that Remote Administration is enabled.
6. Type exit and then type exit again.
Section 3: To enable machine wide, remote access to COM for Anonymous Logon users
1. From the Start menu, click Settings > Control Panel.
2. If using the Classic View, double-click Administrative Tools.
Otherwise, click Performance and Maintenance, and then double-click
Administrative Tools.
3. Double-click Component Services.
4. From the Console Root, open Component Services > Computers > My Computer.
5. If you see a Security Alert dialog box, click Unblock.
6. Right-click My Computer, and click Properties.
7. In the My Computer Properties dialog box, on the COM Security tab, in the Access Permissions group, click Edit Limits.
8. In the Access Permission dialog box, choose ANONYMOUS LOGON, and select Allow on the Remote Access entry.
9. Click OK, and then click OK again.
10. Close the Component Services window and the Administrative Tools window.
Section 4: To enable Anonymous Logon users to have machine wide, remote
activation access to COM
1. From the Start menu, click Settings > Control Panel.
2. If using the Classic View, double-click Administrative Tools.
Otherwise, click Performance and Maintenance and then double-click Administrative Tools.
3. Double-click Component Services.
4. From the Console Root, open Component Services > Computers > My
Computer.
5. Right-click My Computer, and click Properties. This step opens the My Computer Properties dialog box.
6. Click the COM Security tab.
7. In the Launch and Activation Permissions group, select Edit Limits.
8. In the Launch Permission dialog box, click Add, type ANONYMOUS LOGON and click OK.
9. Select ANONYMOUS LOGON, and select Allow on the "Remote Activation" entry. All other boxes should be deselected.
10. Click OK, and then click OK again.
11. Close the Component Services window and the Administrative Tools window.
12. Restart the computer.

My APA Server is installed on a computer running Windows XP with Service Pack2. When APAConsole is attempting to connect to APA Server, “Access denied” appear.
The problem “Access denied” which appears when you try to connect APAConsole to APA Server exists when APA Server works on Windows XP platform with installed SP2. The reason is the increased security of Microsoft when using DCOM. If this is your case please follow the next steps:
STEP1: Choose Local Security Settings from Administrative Tools. The window Local Security Settings will appear. Choose Security Settings – Local Polices - Security Options from the left panel.
Double Click on DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax in right panel. The window DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) will appear. Click button Edit Security, choose Everyone and set check box Remote Activation to be Allow.
STEP2: Run DCOMCNFG.EXE. The window Component Services will appear. Choose Console Root – Component Services – Computers – My Computer – DCOM Config - APACS Object from the left panel. Right click on the APACS Object and choose Properties from the context menu. Choose page Security and click button Edit from Launch and Activation Permissions group. Click button Add and add Everyone to the list. Set check box Remote Activation to be Allow.

I have selected the option to receive popup notification when an event appears,
but nothing happen.
You must check if the Messenger service of the target computer is running.
You can see this in Control Panel - Administrative tools - Services
My APA Server is installed on a computer runing Windows XP/2003 Server. When I try to copy and paste a job “Unable to paste job. The spool file is in use or access is denied” appear even if I’m supposed to have access to the spool file.
On Windows NT/2000 find the files by name xxxxx.spl where xxxxx was the JobID returned by the EnumJobs API. However, XP and 2003 create spool files named FPnnnnn.spl where nnnnn is no longer the JobID.
This is the side effect of file pooling. You can "turn off" Spool File Pooling by keeping printed jobs or specify a different spool directory. The workaround to this is as below:
To Turn Off Spool File Pooling on a Per Printer Queue-Basis
1. Click Start, click Run, type "regedit" in the Open box, and then click OK.
2. Locate the following registry subkey, where <printername> is the name of your printer:
HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindows NTCurrentVersionPrintPrinters<printername>
3. In the right pane, right-click SpoolDirectory, and then click Modify.
4. In the Value data box, type the location where you want the spool files to be stored.
For example, type c:windowssystem32spoolprinters as the default location.
5. Quit Registry Editor.
6. Restart the Print Spooler service.
7. All new jobs will be of the form XXXXX.SPL and XXXXX.SHD and will be numbered consistently with their JobIDs.
To Turn Off Spool File Pooling for All Printers
Note This method only works on Windows 2003 Server. This method does not work for Windows XP.
1. Click Start, click Run, type regedit in the Open box, and then click OK.
2. Locate the following registry subkey:
HKEY_LOCAL_MACHINESystemCurrentControlSetControlPrint
3. On the Edit menu, point to New, and then click DWORD Value.
4. In the New Value #1 box, type DisableServerFilePooling, and then press ENTER.
5. Right-click DisableServerFilePooling, and then click Modify.
6. In the Value data box, type 1 to turn off spool file pooling, and then click OK.
7. Quit Registry Editor.
8. Restart the Print Spooler service.
9. All new jobs will be of the form XXXXX.SPL and XXXXX.SHD and will be numbered consistently with their JobIDs.

After the start the server, I receive error message: “Unable to locate database” from the program.
- Check for the presence of the file "db.mdb";
- Check for the presence of the record "AlagusPrintAdmin4.0" in
"ODBC/System DSN/AlagusPrintAdmin4.0".
If there is not such record, create it and write the path to the file "db.mdb".

I receive error message: “Unexpected database error” from the server.
- It is possible to receive such message, if another application (such as MS Access, SQL Explorer etc) is trying to open the database. Database has option "exclusive”.
- It is possible to have errors in the indexes of the database.
Try ODBS/System DSN/AlagusPrintAdmin4.0/Repair.
If this does not work, the server has to be re-installed.

I receive message. “Unable to connect” after starting APAConsole and filling the fields "APAServer" and "Password".
- Check if there exist a computer with name filled in the field “Server” or if there is APAServer active running.
-  Under Microsoft Windows 95 check the presence of DCOM support. If it is necessary, install it.

I receive message “Unable to locate server interface” after starting APAConsole and filling the fields "Server" and "Password".
- Possible problem with Windows Registry, concerning the registering of APAServer. Re-install APAServer.

The pages "Advanced" and "Environments" in Printer Control Panel are missing.
-  These features are available only for TCP/IP printers, supporting SNMP and PJL.
I cannot see the page "Environments" in Printer Control Panel.
-  The status of the printer must be "Ready - Idle" state. If the printer is busy, this page is not enabled;
-  Check the value of PJL communication port ID. Set it to 9100.

APAConsole has been terminated without any reason.
-  Probably the button “Disconnect Consoles” on the APAServer has been pressed;
-  Possible physical disconnection with the server;
-  The server has been shut down.

According to APAConsole, the status of some printers is "Down", but according to the standard Microsoft Windows "Printers" dialog the status of the same printers is "Ready".
-  This is because Microsoft Windows "Printers" dialog follows only the logical device printer, while APAServer follows the physical print device. (If the printer device is switched-off, APAConsole detects that and the status of the printer goes "Down").

I receive message. “Access denied” after starting APAConsole and filling the fields "Server" and "Password".
-  The DCOM server is not configured properly. Run DCOMCnfg.exe form the server computer, choose “APACS object” from the list click the button “Properties”, click on page “Security” and change default access permission.

The operation “Move” to/from the group Server Local Printer(s) is not available.
- APAServer automatically detect, add and remove these printers.

I receive message “Incorrect password” after starting APAConsole and filling the fields "APAServer" and "Password".
- Administrative privileges are required to start APAServer (APAServer can not access security information).