Difference: SystemAdministratorQuestions (2 vs. 3)
Revision 32016-04-06 - JeanNeron
| Line: 1 to 1 | ||||||||
|---|---|---|---|---|---|---|---|---|
System Administrator Questions | ||||||||
| Added: | ||||||||
| > > | WinAppxD was replaced by the APPX Login Manager in Release 5.0.0. See this page for installing & configuring the Login Manager. | |||||||
| ||||||||
| Added: | ||||||||
| > > | ||||||||
2.1) APPX user ID's that are only 2 characters rather than 3 can't print. Help?This was due to a bug in versions of APPX at or below 3.2.x. If you are running 3.2.x or earlier, you must upgrade to a newer version of APPX or change your APPX User ID's to 3-character ID's. This restriction affects only the APPX user ID's, not the "System ID" that is used to link the APPX user ID with the Windows network user ID. | ||||||||
| Line: 20 to 23 | ||||||||
As of version 3.3 and earlier, this capability is not available. 2.6) We get USER32.DLL errors. Help? | ||||||||
| Changed: | ||||||||
| < < | There are two common reasons that customers experience "USER32.DLL Initialization failed" errors. The first is a Windows NT default resource limit which can be raised by editing the NT server's registry according to instructions at URL: http://support.microsoft.com/support/kb/articles/q142/6/76.asp The second is that the customer is using an old (pre-January 15, 1998) version of WinAppxD.exe. The first thing you should do to resolve these errors is edit the registry as described above. If you have modified the registry and still receive USER32.DLL errors, please contact APPX Software Technical Support to verify that you have the most up-to-date copies of WinAppxD.exe and appx.exe. NOTE ABOUT URL's: Microsoft periodically rearranges its web site, so the above URL may or may not be valid. If you can't find it, use the "Search" option on the MS web site, instructing it to look in whatever choice includes the "Knowledge Base". Specify "Qnnnnnn" as what to look for, where nnnnnn is the number between the "q" and the ".asp". For example, in the above, it would be Q148367. That should enable you to locate the article. | |||||||
| > > | There are two common reasons that customers experience "USER32.DLL Initialization failed" errors. The first is a Windows NT default resource limit which can be raised by editing the NT server's registry according to instructions at URL: http://support.microsoft.com/support/kb/articles/q142/6/76.asp The second is that the customer is using an old (pre-January 15, 1998) version of WinAppxD.exe. The first thing you should do to resolve these errors is edit the registry as described above. If you have modified the registry and still receive USER32.DLL errors, please contact APPX Software Technical Support to verify that you have the most up-to-date copies of WinAppxD.exe and appx.exe. NOTE ABOUT URL's: Microsoft periodically rearranges its web site, so the above URL may or may not be valid. If you can't find it, use the "Search" option on the MS web site, instructing it to look in whatever choice includes the "Knowledge Base". Specify "Qnnnnnn" as what to look for, where nnnnnn is the number between the "q" and the ".asp". For example, in the above, it would be Q148367. That should enable you to locate the article. | |||||||
2.7) Where are the instructions for interfacing with UniQue?Instructions for interfacing APPX Presentation Manager with the UniQue print spooler from LBM Systems can be found here. | ||||||||
View topic | History: r3 < r2 < r1 | More topic actions...
Copyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding TWiki? Send feedback