LightSpeed NVS Problems & Solutions

Problems/Error Messages (click to view solution) [ALL SOLUTIONS]
●	0X14 - No Lightspeed [LS] Server Found
●	928 g/w's are locking up while SCSI g/w's are attached at the same time
●	All servers must be detached before VSBIOS may be authorized
●	Any LAN bound attachments. LGTWPUT error: -55 ErrorText: -55 ProbableSolution: -55
●	Applet Terminated
●	APPMODUSR reports the "user not found" on VS bound dirsync
●	AST Bravo MS and Wang WLOC brd, Unable to Connect
●	Banyan error 152
●	Blue screen of Death in WinNT, Access Violation in 95/98 when exiting VT and using certain ATI video cards
●	Border Manager Software installed = VT not working
●	Cannot create the VS target file"\.....\...." (Ext.) Invalid WP+ filename
●	Cannot Find the Lightspeed Server using Multiple NIC cards or A NIC and the "Dial-Up Adapter"
●	Cannot remove/delete 6 .DLL files on NT clients only when doing an LS upgrade
●	Cannot rename LS and LSDATA for Upgrades
●	Cannot see any Libraries when using Filex
●	CCMGTW\TEMP subdirectory is deleted on LANSERVER
●	CCMUSERS.KEY is Corrupt
●	cc:Mail IMPORT returns 1 "Error mixing command line syntax"
●	DMS OPEN Error Exit reported the following problem: Output file already exists or non-output file not found. Prname = SYNCTRN, filename = MSYNCATT, library = LSMSMDAT, volume = xxxxxxxxx, records = 0, mode = INPUT. Problem reported at location 31.
●	Document Conversions not authorized [past 1 page]
●	DOSIMPORT / DOSEXPORT support in office
●	Dr. Watson errors on NTLspeed gateways, Intermittent Lock-Ups
●	Dynamic Fonts do not work properly
●	Error 0 from VnsDosConnect()
●	Error 0 opening session on VS
●	Error 114 Logins Inhibited
●	Error 20 on Banyan clients
●	Error 3068 during Mail Migration
●	Error Addresses Read = 0
●	Error Binding Network Address
●	Error in command line parameter. IMPORT process ended with error: 3
●	Error IN07 reported by con in active subprogram LSZ80DRV. Unable to proceed because of unexpected response by LOADCODE request. Operating system response = 101. Initializing of the CWP environment stops with no response and no "merged" document.
●	Error mapping VS Login ID, Error 16
●	Error opening database; error=4
●	Error Starting Program LSVT.EXE; Linked to missing export FXCONFIG.DLL:_fxconfigFREE@4
●	Error Starting Service: Unable to open device "{hhhhhhhh-hhhh-hhhh-hhhh-hhhhhhhh}"
●	FATAL - {wpo_synw.c,1873} Found unexpected users already existing in the groupwise/WordPerfect Office gateway 'AHB'. Cannot continue the synchronization until these users are removed
●	Fatal error issuer _swap shell problem cannot open the temporary swap file, attempting to execute Y:\lsmsm\lgtwget.exe location return code 9 reported in problem msmailer.cpp at line number 1400
●	FAULT 4 - CONVERTING PROTRAIT DOCUMENTS
●	File not found MSORTAT0
●	Foreign Characters do not convert correctly
●	Gateway hangs preparing cc:Mail message
●	Gateway hangs when processing Lan bound email
●	Get parm, LS Rex RC error - Dos Input
●	Getting Postscript Errors when printing from Microsoft Excel using WVSPOOL
●	GPF when trying to use the Print Window feature - version 2.2.0 (-)
●	Groupwise to Exchange Dirsyncs
●	How to Authorize Lightspeed NVS Products While Lightspeed NVS is In Use
●	I need to Uninstall WebConvert; how?
●	IP Magic Appliances: Unable to obtain a DHCP address through Microsoft TCP/IP stack
●	IPX Errors when invoking VSTW or Filex
●	Is it possible to install to another volume, authorize it (temp codes) and then move that copy over to the correct volume without causing any problems?
●	ISSUER: LS API register_session PROBLEM: (102) SOLUTION: (102)
●	Line 21 failed to connect to the mailbox
●	Local Requestor Not registered
●	Location = 5, Error Code = 254. Macsoft microcode is no longer loaded in the WLOC card.
●	Logins Inhibited
●	LS Print redirector would stop printing for no apparent reason
●	LScopy Error, cannot open the VS source file; (open) access denied by LS security
●	LSMGR CANNOT INVOKE VSBIOSCI - RETURN CODE 80
●	LSpeed caused an invalid page fault in module lsclient.dll at a memory location 0137: 004541ed
●	Mailbox name, the password or both are missing or are not authorized or are in the wrong format
●	Max number of files are already open, add FILES=xxx to your CONFIG.SYS error 4
●	Maximum sessions already open, Error = 100
●	Maximum Subtask Quota to small, change in Security. Unable to invoke Subtask.
●	Message sender not listed in VS directory
●	Missing the (80th column) within VT
●	MSMAIL SRV main report following problem - 1
●	MSMap Error, return code = 092
●	No system name has been specified for this instance of LS and none can be found in the LS configuration. LS needs to be configured for use on this workstation.
●	No valid recipients when processing Lan Bound mail. We found a broadcast message in the Queue and deleted it now everything is fine.
●	NTLSPEED hangs. The problem will be fixed by the time that 2.2.0 is released
●	Open Process Timeout Errors
●	Open SPX connection timeout, check maximum data size SP = parameter
●	PC hangs during install while displaying "Authoring WP Conversions"
●	PCI Bus Video Card with WLOC board
●	Print jobs have garbage character(s) in the upper left hand corner of the first page
●	Prioritizing Win32 LS traffic via Routers
●	Processing Loop Detected
●	Pseudo blanks are dashes
●	Pseudo Blanks are not being copied correctly
●	Return code 2 reported in program MailServ.CPP
●	Return code R001 from Data Management System OPEN
●	Routine DOS_open, path not found
●	Runtime error r6003, integer divide by 0
●	SCSI chain hangs and inactive LS SCSI Servers
●	Service Pack 3 Bugs
●	Several issues have been fixed on the NT gateway. (2.4.0+)
●	Support for Lower/Upper Case Letters for Print Classes, 26+ ?
●	SvcDoCommand() rcv'd unsupported command '5'
●	SYMPTOM: Error xx setting current mapped disk drive to X:
●	The 91st client receives an "Error 121, Timeout has Expired" when trying to attach to a SCSI gateway
●	The following files in C:\MSMSTDA.DAT\ were not found or could not be accessed: SPCLMBXS.D01
●	The procedure entry point WNetCachePassword could not be located in the dynamic link library MPR.dll
●	Unable to invoke subtask, return code = 055
●	Unable to mount device LSR##### and fails with a return code of 12. If the @MCRCU file is release 1.07.7 or later it will fail to bring up Lightspeed SCSI gateways.
●	Unable to mount device LSR##### and fails with a return code of 12. If the @MCRCU file is release 1.07.7 or later it will fail to bring up Lightspeed SCSI gateways.
●	VATTACH processes successfully; VT or VSTW fails
●	Vclient.exe - PC hangs, possible solution (?)
●	Vines Error 163
●	VS error performing directory sync error code=0, return code=5, extended VS code
●	VS print jobs going to another unspecified LS printer
●	VSBIOS 3.20.00 goes into debug
●	VSBIOS SCSI Transport Location 5001, Error = 0x1388
●	VT session failure(s) using Shiva Lan Rover
●	VT will try to connect/start the Internet Dialer
●	When running the IP Magic Manager or the IP Magic Authorization program: "There was an error communicating with the license service. Please execute the setupex.exe in the directory where the IpMagic Server is installed"
●	When using VSPOOL the print job goes to the remote VS, but ignores the PRINTCLASS setting and goes to the Class "A" printer
●	Win32 error: 5 - Access denied
●	WP+ printing suspended / WP Plus printing suspended
●	WP+ Support needed, without re-installing LS s/w
●	Wserver hangs when starting WFW
●	WW6=xxx is not supported
●	Error in Command Line when trying to invoke Wserver
●	Error writing to (printer port ) for the printer (printer created) the system cannot write to the specified device
●	Invalid Password using a Wang 724 Keyboard on a Win95 PC
●	Issuer: _swapshell. Problem - the program to be executed was not found. Details - attempting to execute REQMAIN. Location - Rtn Code 2 reported in program MSMAILER.cpp @ line 4497, press ESC to exit. When performing a dirsync
●	New Media Player (by MicroSoft) problems with VT
●	No job class L" initiator or not enough memory"
●	Unable to find the LS server from a remote client's location
●	Unable to start a print job, the parameter is incorrect
●	Unsupported Function on a Dell Latitude XPI-CD PC
●	(@MCRCU@) Installation of 7.52.xx onto a VS 5000 series loses SCSI g/w communications

Solutions

0X14 - No Lightspeed [LS] Server Found

Customer must use the /I=xxx switch in the VATTACH command line to specify the correct network segment [Network ID] that the LS Gateway is on. Customer can type in 'USERLIST /A' to verify the correct Novell Network / segment from their DOS prompt if they're Logged on. The screen should have a column called NETWORK, this will show the Internet segment numbers [or letters] for all users that are logged on. The asterisk on the left side will be the current user that typed in USERLIST /A. These Network numbers and/or letters are needed for the /I= switch. i.e. /I=2 or /I=emb123. Left edge or leading '0's can be omitted from the switch entry. Customers must also assure that the Router(s) and or Bridge(s) are NOT filtering IPX Packet Type 0 [zero]. If if Packet 0 is being filtered then IPX Address Sockets F463 and F563 should NOT be filtered. Lightspeed uses registered address sockets F463 and F563 for "Broadcast" and "Connection" respectively, and both are Packet Type 0 [zero].

928 g/w's are locking up while SCSI g/w's are attached at the same time

Change the timeout buffers by 50% and the gateways haven't hung since. Increase it. On the VS, under LS Configuration, the "Set 928 Options". Go from 9000 to 13500 on the timeout buffers. We did this because we had seen on a "hung" 928 gateway that there were 3 Read buffer timouts. Based on a paragraph in the documentation that suggested a 50% increase for Read buffer timeouts, we made the change and haven't had a problem since. This change was just for the 928s, though. We haven't opened up the SCSI gateway for everyone yet.

All servers must be detached before VSBIOS may be authorized

From a VS workstation NOT an LS client or single, run LSCANCEL and LSPRTOFF from library LS. If you still get the error make sure that the VSBIOS program is not included in FASTLINK.

Any LAN bound attachments. LGTWPUT error: -55 ErrorText: -55 ProbableSolution: -55

If Novell, load VSBIOS before LSLs or NETX.

Applet Terminated

Delete all inetcfg.lsx files.

APPMODUSR reports the "user not found" on VS bound dirsync.

Run MS-Mail ADMIN and modify the group, press enter through all the screens and the group will be verified and corrected.

AST Bravo MS and Wang WLOC brd, Unable to Connect....

Add the Wang WLOC card to the system and install. Add Vboard in ISACU, IRQ=11, I/O=342h, EMM386 exclude D000-DFFF.

Banyan error 152

Cisco resolved the problem by upgrading the router software to release 11.1.6 in order to take advantage of an option to "ignore packet errors" and pass the packets with errors over the router anyway. "MAC layer mismatch errors" showed up on the network sniffer trace in Lightspeed packets, even on the "local" segment. Local segment users did not experience connection problems, but these errors were "stopped" at the router for remote segments and hence the Banyan 152 error. With this version of the Cisco Router software the problem is now resolved.

Blue screen of Death in WinNT, Access Violation in 95/98 when exiting VT and using certain ATI video cards.

Jeff Bidgood has come through big time, the problem with the BSOD/Access Violation when exiting VT has been resolved. For WinNT the solution was to apply SP5. For Win95/98 the solution is to download and install the latest ATI Rage 128 VR AGP (English) driver. File version is 4.11.6114

Border Manager Software installed = VT not working

They need to copy the Winsock.dll and Wsock32.dll to the [local or network drive] of LSNVS before activating Border Manager. When Border Manager is activated, the .dll's under System are swapped. This no longer has an effect with LS because it is now using the .dll's within the client's LSNVS sub-directory.

Cannot create the VS target file"\.....\...." (Ext.) Invalid WP+ filename

Check for these items: 1. Suppress WP Plus Directory Display Mode needs to be checked. Under fxconfig.lsx, VS Settings. 2. The file naming convention should only be an "AFxxxxxx" name. The VS will not recognize any other name for WPPlus. You cannot use any other beginning of the name (AF......) or you will get a invalid ext. Also, you can use the "NEXT" function which will name the AF...... files with the next number in line.

Cannot Find the Lightspeed Server using Multiple NIC cards or A NIC and the "Dial-Up Adapter"

It has been known for some time that a machine with either: 1) Multiple NIC cards or 2) A NIC and the "Dial-Up Adapter" (for Internet Connectivity). will create 2 IP addresses on the machine (this is what is called 'multi-homed'). With LSNVS/32 we saw behavior wherein (in most cases) if both interfaces were active on a machine (NT/95/98) user's would receive a "Win32 Error 121 - Timeout Expired" when connecting via LSVT. This was found to be because we were sending out the "search" packet on the wrong interface. That is to say, the LS gateway is on the LAN, a user is connected to the Internet, and when we try to find the gateway we send our UDP packet out to the Internet instead of the LAN. One solution was to put the IP address of the proper NIC or DUA in the "Network Client" field in the LSCONFIG.LSX file. This forced LSNVS/32 to use the IP Address (and the interface) that was in this field. This worked best for 2 NICS or DUA that used STATIC IP addresses. When DHCP or any other dynamic IP address configuration protocol was in place this usually was not a good solution since the address would change on each re-connect or after a timeout period. Another solution for NT clients was to DISABLE the NIC (or just TCP/IP on the NIC) that was not in use when the DUA was in use and this (again) would more than likely solve it. But there was not a similar solution for 95/98 clients. What was recently found out was that there is a way to tell WINSOCK to bind to the "proper" interface when sending this UDP packet out (and all other packets as well). This is done by using the special address of "0.0.0.0". It's not a VALID IP address of any machine, but it's a special "flag" that tells Winsock to use its internal methods to bind to the proper interface. I found (using some Winsock SNIFFER tools that most other WINSOCK apps (Netscape, IE, WSFTP, etc) use this method as well). How does it work in LSNVS/32? In the LSCONFIG.LSX file there is a "Network Client" field for each VS. This is used only for TCP/IP gateways and usually populated with "%MACHINE%" by default. If user's of multi-homed PCs or PCs with Dial-Up Networking and a NIC put in "0.0.0.0" instead they should not experience any trouble.

Cannot remove/delete 6 .DLL files on NT clients only when doing an LS upgrade

Go to Control Panel, Services and STOP the Spooler. Then apply the patch / Upgrade, now restart the Spooler.

Cannot rename LS and LSDATA for Upgrades

They should run LSWSNOFF (our subroutine to terminate the communication support) then try renaming the LS libraries. This will also work if they cannot get access to the LSCONFIG file.

Cannot see any Libraries when using Filex

Check: Make sure that this user (or all users) have access rights to the DP/WP/WP+ Libraries from LSmenu/configuration/User Options Mgt, also check the MSDOS redirector and make sure it being started -- it should be set to YES. Make sure that Secure access is set to NO. Check config.sys, Files=50, Buffers=30, Stacks=0,0 (?) this is wrong -- change it to read: Stacks=9,256. Have the Lastdrive=E (or D) statement set in Config.sys Have the SET LS=C:\???? ?=LS or LSDATA or ?? another suggestion: Delete the wvstw.prf, wfilex.prf and lsconfig.prf and re-input data into lsconfig. Filex should now show all of the VS Libraries.

CCMGTW\TEMP subdirectory is deleted on LANSERVER

Download CCM_RUN.ZIP from the BBS. This did not constitute a full upgrade.

CCMUSERS.KEY is Corrupt

Run KEYBUILD.EXE CCM_DB from the gateways DATA\ directory to rebuild all the index and key files.

cc:Mail IMPORT returns 1 "Error mixing command line syntax"

If the cc:Mail Post Office name does contain spaces try and get them to remove the spaces since they could also be invalid PO names elsewhere in the ADE cycle. If they won't change, then try inclosing the PO Name in quotes in the gateway configuration.

DMS OPEN Error Exit reported the following problem: Output file already exists or non-output file not found. Prname = SYNCTRN, filename = MSYNCATT, library = LSMSMDAT, volume = xxxxxxxxx, records = 0, mode = INPUT. Problem reported at location 31.

A quick fix would be to run the LSMSSTAT program (change mail server status) and set the directory synchronization status for MS-Mail to zero (what is it now?) and remove the next mail item in queue in ms-mail using ADMIN. Can be caused by incorrect Network or PO for the directory server in GTWMENU.

Document Conversions not authorized [past 1 page]

LS DOS document conversion (DCOPY) is limited at each workstation until VCONAUTH is run at the PC after connecting to the VS via VATTACH and conversion authorization is successful. Appropriate authorization codes have to be input on the VS prior to running VCONAUTH. The non-authorized process will convert ONLY the first page of each document selected. The FILEX program (run in the Windows environment) will do FULL document conversion, with or without the VCONAUTH authorization process being run. This is a known discrepancy in the Windows License.

DOSIMPORT / DOSEXPORT support in office

These two options are not provided by LS. @NETSHR@ IN @MSDOS@ ON SYSVOL

Dr. Watson errors on NTLspeed gateways, Intermittent Lock-Ups

Operation of the Lightspeed Gateway is halted and all clients attached go inactive ( lockup the Lightspeed attachment and sessions ). The gateway PC can be restarted normally (power down or restart) or the Lightspeed Gateway application can be restarted with normal operations returning until the next failure. This failure can occur on multiple gateways intermittently. Examination of the Dr. Watson error logs should reveal the suspected culprit which is a client with a "corrupted" LSCONFIG.LSX file. This is indicated in the "Raw Stack Dump" section of the drwatson.log file, looking for the 'Disconnect Client' entry in the ASCII Text translation, which will be followed with the client's IP Address and client name. The noted client should have it's LSCONFIG.LSX file rebuilt or replaced.

Dynamic Fonts do not work properly

Install Microsoft Plus Pack. Apparently, the Plus Pack fixes a few of the errors that Win95 has. Once this is installed, the Dynamic Font option will start to work.

Error 0 from VnsDosConnect()

remove the quotes, stop and restart the service

Error 0 opening session on VS

If WIN /S works then upgrade VIPX.386 and NWIPXODI.DLL. There is a good version on the Lightspeed BBS in VIPX.ZIP. Also add the following lines to the [386Enh] section of the SYSTEM.INI file: Int28Critical=false Int28Filter=2

Error 114 Logins Inhibited

When using VT emulator and customer performs an IPL with Logons Inhibited, the QUEUE file in @SYSWORK on the customer's system volume may have been corrupted. Customer will need to IPL from an alternate volume, scratch this file and then IPL from the original system volume. This will recreate the QUEUE file but the customer will have to recreate initiators, WSN and DP Print schedule information.

Error 20 on Banyan clients

Here are some things to check, these are processes that have remedied the Error 20 for other Banyan clients. Run PCCONFIG from the client PC and change the following: [4. Communications Settings] 1. Set Communication Buffer Size ----> Max out to 60 2. Set Maximum Number of Open Sockets -> Max out to 60 3. Set Maximum # of Open SPP Connections -> Set to 75. Documentation error... the VATTACH command states that /C=60 to 32000 would be valid, but we've determined that 200 is the minimum and 32000 is valid. The "error reserving Banyan sessions=20" message is basically returned when the Gateway does not respond to the client Vattach. This can be caused by network delays that can be adjusted for with the timeout parameter (/C=xx) on the VATTACH. One way to test for appropriate timing values would be to use the BANTEST program to test the link between the Gateway(s) and the client /network segments: Run BANTEST /N=99 on the gateway machine and BANTEST /C /N=99 from a client on each network segment. Note the timing information returned for a 1mb test and use these values to adjust the VATTACH command. Banyan ports 256, 257 and 258 are used by Lightspeed for "Search" and "connection". In reviewing Banyan's current and previous "Developer Toolkit" notes, these ports 256-511 are listed as Reserved for 3rd party applications - Do Not Use and as such are not typically listed in Banyan's "list of well known ports" and could possibly be filtered or excluded for the purpose traffic control at each or any of the routers in the your network. This issue of possible port filtering should be immediately addressed by the router manufacturer or your network administrators or service providers. This of utmost importance that they allow the processing of information passed to Banyan ports 256, 257 and 258.

Error 3068 during Mail Migration

This is a Vines problem, the best way to get around this problem is under Mail Migration, check the box for Unattended Operation. This will by-pass the Error 3068 from stopping the migration process and continue with the migration, then they can view the log file, get the message ID from that log file, then they can view the file contents from within the Mmail utility.

Error Addresses Read = 0

This is caused when the customer installs the gateway and they create the \MSMGWDAT (data) directory as a subdirectory under Exchgw instead of off the root of the C:\ drive. The default installation of the gateway places this data directory off of the root of C: It's also recommended that you do not use a dot (.) in the directory name.

Error Binding Network Address

The Protocol that the Lightspeed Client is using (i.e. TCP/IP) does not have a client "bind" specified in NETWORK setup properties. Install the "Client for Microsoft Networks" support through the Control Panel / Network option and assure that the protocol that Lightspeed services will be using is specified in the Bindings option of the protocol's "properties". ie TCP/IP. If this is still a problem, Delete the network properties and reInstall them, reboot, and test again. Explanation: Some Win95 workstations may network primarily with a different protocol than the Lightspeed configuration is using(i.e. Banyan Vines Client for Windows 95 which is a unique and separate protocol). When the Lightspeed protocol is added to the Network Components list it is possible to ignore the binding information, which means that Win95 will not start that protocol and the above message will be displayed when Lightspeed attempts a connection to the Gateway.

Error in command line parameter. IMPORT process ended with error: 3

IMPORT.EXE version 5.1 CCMVSO version 1.17 or prior IMPORT 5.1 is not backwards compatible with earlier version although it is documented to be. Must upgrade to CCM_VSO version 1.18 IMPORT.EXE version 5.1 CCMVSO version 1.18 You should only see this error if performing an unsync of VS names from cc:Mail.

Error IN07 reported by con in active subprogram LSZ80DRV. Unable to proceed because of unexpected response by LOADCODE request. Operating system response = 101. Initializing of the CWP environment stops with no response and no "merged" document.

Make the following adjustments to the VTCONFIG.LSX file: In the client Master VTCONFIG.LSX file (access through Manage Configuration in the client software) open the tab group for "WP/WPPlus"; in the "WP/WP+ Options" section, select "Emulate 4230 Workstation", de-select "Keep WPIDS file on PC" and de-select "Time take from PC". In the "Document Storage" section, select "Keep on VS only" which de-selects the "Cache on PC" option. Save these changes to the Master VTCONFIG.LSX file by clicking on "OK". This forces the document to be indexed and stored on the VS only which will not conflict with the application. By the way, MADES II and BCAS are third party "Contracting" applications used specifically by the military.

Error mapping VS Login ID, Error 16

Changed the minimum Alias length to 3 characters and everything worked. Looks like LSOFSERV uses the literal Vattach userID for office calls rather than mapping it back to the 3 character ID.

Error opening database; error=4

That error typically means that the "d_open()" call was unable to find the database - specifically, the file VCC_DB.DBD. See how much free environment space is being allocating in CONFIG.SYS with the "SHELL=COMMAND.COM /E:xxxx" command. Recommend at least 1k (1024) as the 'xxxx' part.

Error Starting Program LSVT.EXE; Linked to missing export FXCONFIG.DLL:_fxconfigFREE@4

Under Windows Explorer\View\Options the Show All Files should be selected. If this isn't, then all the files won't get copied over. Also make sure that before applying the patch files, reboot this client PC if LS has been invoked at all.

Error Starting Service: Unable to open device "{hhhhhhhh-hhhh-hhhh-hhhh-hhhhhhhh}"

Uninstall and Reinstall the Driver: Follow the instructions below on the IP Magic server machine. Windows NT 4.0 Machine: 1. Open the Network control panel. 2. Select the Protocols tab page. 3. If the IP Magic Interface Protocol or IP Magic Intercept Protocol is displayed in the list of network protocols; a. Select 'Remove' and then 'Yes' to uninstall the driver. b. Select 'Close' on the Network control panel dialog and then restart the machine. WARNING: You must rebind the network protocols to the network cards before rebooting if you need network access to logon as an administrator. Open the Network control panel to the Bindings tab page. In the 'Show Bindings for' pull-down, select 'all adapters'. Right click each adapter and select 'Enable'. Now restart the machine. This is unnecessary if you can logon as the local administrator. Also, the bindings will be corrected when the driver is reinstalled. c. After reboot, open the Network control panel to the Protocols tab page. 4. Click 'Add...' to Select the Network Protocol. 5. Click 'Have Disk', enter the path to the driver files. The default location is C:\Program Files\Lightspeed Systems\Total Control\WinNTInterfaceDriverInstall or ...\WinNTInterceptDriverInstall. Select 'OK'. 6. The Select OEM Option dialog should open with the IP Magic Interface/Intercept Driver highlighted. Select 'OK'. 7. After the driver is installed and displayed in the list of network protocols, select 'Close' on the Network control panel dialog and restart the machine. Windows 2000 Machine: 1. Open the Network and Dial-up Connections control panel. 2. Select a network card and click File | Properties. 3. If the IP Magic Interface Driver or IP Magic Intercept Driver is displayed in the list of components; a. Select 'Uninstall' and the 'Yes' to uninstall the driver. b. Select 'Close' on the properties dialog and then restart the machine. c. After reboot, open the Network and Dial-up Connections control panel, select a network card, and click File | Properties. 4. Click 'Install...' to select the Network Component Type: a. Select 'Protocol' to install the Interface driver, or b. Select 'Service' to install the Intercept driver. 5. Select 'Add...' and then 'Have Disk...' to 'Browse...' to the driver files. The default location is C:\Program Files\Lightspeed Systems\Total Control\Win2kInterfaceDriverInstall or ...\Win2kInterceptDriverInstall. 6. Select IpmInterface.inf or IpmIntercept.inf and click 'Open'. Then click 'OK' to accept the path. 7. The Select Network Protocol dialog should open with the IP Magic Interface/Intercept Driver highlighted. Select 'OK'. 8. After the driver is installed and displayed in the list of components, select 'Close' on the properties dialog and restart the machine. You should now be able to start the service successfully.

FATAL - {wpo_synw.c,1873} Found unexpected users already existing in the groupwise/WordPerfect Office gateway 'AHB'. Cannot continue the synchronization until these users are removed.

If they entered an existing Groupwise PO as the gateway PO then they need to respecify in the gateway configuration. If this is a gateway that has been synced in the past and gateway DBFs have been initialized then the gateway users should be removed from Groupwise.

Fatal error issuer _swap shell problem cannot open the temporary swap file, attempting to execute Y:\lsmsm\lgtwget.exe location return code 9 reported in problem msmailer.cpp at line number 1400

Delete all T*.xxx file in LSMSM

FAULT 4 - CONVERTING PROTRAIT DOCUMENTS

When converting portrait documents Page Setup - Margin is Top & Bottom set to 0.5 should be 1 inch this corrects the pagination. Document: AF2466.

File not found MSORTAT0

Run Program LGTWPUT without any parameters. This was Fixed in Version 1.05.01

Foreign characters do not convert correctly

Under Manage Configuration go to FXconfig.lsx (the File Exchange configuration file) make sure that the appropriate character set (ie FRC) is chosen and either International ANSI or International OEM are being used.

Gateway hangs preparing cc:Mail message

Make sure the gateways subdirectory TEMP exists.

Gateway hangs when processing Lan bound email

Make sure there is a subdirectory TEMP in the gateways home directory.

Get parm, LS Rex RC error - Dos Input

#1. Check that the LS MS-DOS redirector is running. #2. Check LS and VS Security for access to WOWORK and ENVLIB . #3. Make sure that LS DATA VOLUME in SETSYSOP in not blank. #4. Check that Directory scan secure is set to NO for the vattach user id. #5. Make sure the editor program can be executed. Run OFFICLNK select User Administration.OFFICE/Link MS-DOS Definitions and make sure the application program specification contains the full path to the application or that the application EXE is in your path.

Getting Postscript Errors when printing from Microsoft Excel using WVSPOOL

Increasing the VSPOOL / WVSPOOL timeout setting solved this Windows printing problem.

GPF when trying to use the Print Window feature - version 2.2.0 (-)

Upgrade to the minimum version of 2.3.0.

Groupwise to Exchange Dirsyncs

Delete the Remote requestor in Exchange then delete the gateway network/postoffice from the Address Space tab (MS Mail Connector). Change the Gateway Network/Postoffice in GTWMENU on the gateway itself and press F10 to save. Add the new Network/Postoffice to the Address Space Tab of type MS. Create the remote requestor again selecting the "new" network/postoffice. Make sure all Exchange services are running. All Done!

How to Authorize Lightspeed NVS Products While Lightspeed NVS is In Use

PROCEDURE: Follow these instructions to authorize Lightspeed while it is in use: 1) Copy the programs VSBIOS and LSINAUTH (928) and/or VSBIOSCI and LSAUTHSI (SCSI) from LS on the Lightspeed volume to a temporary location (to any other library on any volume). To do this: 1A) Run BACKUP. 1B) PRNAME = SPEED: Press ENTER to perform a normal DMS backup. 1C) PRNAME = INPUT: Enter VOLUME=<Lightspeed volume>, LIBRARY=LS, FILE=VSBIOS, and MOREFILE=YES. And then press ENTER. 1D) PRNAME = MOREFILE: Enter LIBRARY2=LS, FILE2=LSINAUTH, LIBRARY3=LS, FILE3=VSBIOSCI, LIBRARY4=LS, and FILE4=LSAUTHSI. And then press ENTER. 1E) PRNAME = OUTPUT: Enter a temporary library and volume in the VOLUME and LIBRARY fields. 1F) PRNAME = OPTIONS: Enter DUPFILES=PROMPT and then press Enter. 1G) PRNAME = LOGFILES: Enter OUTDEV=NO and then press ENTER. 1H) PRNAME = EOJ: Press PF16 to terminate BACKUP. 2) Run the program LSINAUTH (928) or LSAUTHSI (SCSI) in that temporary location. 3) Contact Lightspeed Software or your international dealer to obtain your code(s). If you are obtaining a permanent code, write down this code for future reference. 4) At a time convenient to you (i.e., during the next backup/maintenance cycle), copy and overlay the files in the temporary location back to the library LS on your Lightspeed volume. 5) Scratch the files in the temporary location.

I need to uninstall WebConvert; how?

There are a few ways to make sure that WebConvert is fully removed from your hard drive. *Note- Please be careful when using Regedit or reg32edt. If you make a mistake while using the program, it can damage your computer. Lightspeed Software is not responsible for any mistakes that you make. These are the following steps: Step 1) Click on Start Step 2) Click on Settings Step 3) Click on Control Panel Step 4) Double click on Add/Remove Programs Step 5) Highlight WebConvert Step 6) Click on Add/Remove Step 7) After it is done uninstalling, click the OK button Step 8) Then, click on the Start Button Step 9) Click on Programs Step 10) Click on Windows Explorer Step 11) Go to the directory you installed WebConvert, and verify that it has been deleted. (Default installation directory \Program Files\Lightspeed Software\) Step 12) Close Windows Explorer Step 13) Using the Right mouse button, Click on the Start button Step 14) Choose the option for Explore Step 15) Double click on Programs Step 16) Verify that the WebConvert Folder has been deleted Step 17) Close the Windows Explorer Step 18) Click on Start Step 19) Click on Run Step 20) Type "regedit" (Win95) or "reg32edt" (WinNT) Step 21) Verify that the registry key has been deleted. (HKEY_LOCAL_MACHINE\Software\Lightspeed Software\) *Note- Please be careful when using Regedit or reg32edt. If you make a mistake while using the program, it can damage your computer. Lightspeed Software is not responsible for any mistakes that you make.

IP Magic Appliances: Unable to obtain a DHCP address through Microsoft TCP/IP stack

Reset the DHCP Client service to "automatic" NOTE: The DHCP Client service is not required in anyway for the IPM Interface Object's ability to acquire a DHCP address when configured to do so, however you should not have both the IPM Interface Object and Microsoft tcp/ip stack configured for DHCP at the same time.

IPX Errors when invoking VSTW or Filex

Switch to SPX drivers; Sserver and Sclient.

Is it possible to install to another volume, authorize it (temp codes) and then move that copy over to the correct volume without causing any problems?

Remember that VSBIOS or VSBIOSCI are the modules being authorized... run LSINAUTH from the "new" library or run "Menu" from the new library and drill down to the authorization routine. Here's what to do: 1. Install new LS into vol2 \ LS and vol2 \ LSDATA 2. Run vol2 \ LS \ LSINAUTH - authorize modules 3. Rename vol1 \ LS as vol1 \ LSOLD 4. Rename vol1 \ LSDATA as vol1 \ LSDATAO 5. Copy vol1 \ LSDATA \ LSCONFIG to vol2 \ LSDATA 6. Copy form and font files from vol1 \ LSDATA to vol2 \LSDATA 6. Run vol2 \ LS \ LSSETOPT and change "Data Volume" to vol2 (save changes) 7. Done...... delete old libraries

ISSUER: LS API register_session PROBLEM: (102) SOLUTION: (102)

Check that a copy of LSMSMSRV is not running as a background task on the VS. If its not then some other VS application is using the ITM port name LSMR

Line 21 failed to connect to the mailbox

After verifying that the Help file instructions found in the section on "Migrating to Existing Exchange Mailboxes" have been followed, if you still receive this error Move the .PKL, .PRI, and .SEC files to the Exchange server you are migrating to and run the Migration Wizard.

Local Requestor not registered

Upgrade MSMail Admin program to version 3.2.3 or register the gateway PO as outlined in the manual Page 4.13

Location = 5, Error Code = 254. Macsoft microcode is no longer loaded in the WLOC card.

The problem is that the WLOC board dropped Microcode to the VS. Meaning the connection is no longer valid. A power failure is one of the reasons that you would get this error. The other is when there's a memory address conflict between the WLOC board and the NIC (Network Interface Card). Make sure there's no address conflict between these two card or any hardware device that is being used on the Lightspeed gateway. Also check the gateway's Config.SYS file and make sure you're excluding the WLOC and NIC address on the EMM386.EXE line. Try moving the WLOC's address into a different memory segment to avoid device conflicts. The valid addresses used for the WLOC board are A000, D000, and E000. Try the following test: Take Lightspeed out of the picture and reboot the gateway PC. Make sure the network and other drivers are also being loaded (except for Lightspeed. i.e., Sserver/Vattach). Then, from the LS directory run the following command from the DOS prompt: WLOC /J=A000 or /J=D000 or /J=E000 Depending on the address that you selected, if you get a clean VS Logon Screen and can LOGIN to the VS using the gateway's user id and password is an indication that the address selected is good and its available for the WLOC card. The last step is just to make sure that you change the 928 Address in VCONFIG and exclude that memory segment on the gateway's Config.SYS file. See example below: If my WLOC board is using memory segment A000 and my NIC is using C800-CFFF, the following EMM386.EXE line would look something similar to the line below: DEVICE=C:\DOS\EMM386.EXE NOEMS X=A000-AFFF X=C800-CFFF P.S. You may also check a memory region's availability by running Microsoft's MSD program.

Logins Inhibited

The suggestion for the users is if they need full security on their system, then go ahead and use the Lock User ID (optional: Continue impression of attempts) So, the user will not need to recreate their Queue file every time this error happens. This can be set using VSSECURE (not Security), use PF3, PF2.

LS Print redirector would stop printing for no apparent reason

If a VS volume had VTOC problems then the LS Print Redirector would stop. After running LISTVTOC on all volumes it [should] correct the problem with the redirector stopping.

LScopy Error, cannot open the VS source file; (open) access denied by LS security

There are (3) three possible solutions in order to resolve this: 1.) On the Client PC that is having the trouble, delete the FXCONFIG.LSX file. The FXCONFIG.LSX file is a text based configuration file for Lightspeed. It will get recreated automatically. 2.) Log onto the Wang VS, and run the program Menu in the LS library. Then, choose the option for Configuration and choose User Option Management. Check the userid and make sure they are not excluded from the library. The way User Option Management works is if the user is Included in 1 Library or Volume, then the user is Excluded from the rest. This works vice-versa as well. 3.) The last option is to download the 2.0.8 version of Lightspeed. The file is patch95.zip, just as it was before, and the password on the file is lsnvs200. Download the file at ftp://ftp.lightspeedsoftware.com/wip/lsnvs/.

LSMGR CANNOT INVOKE VSBIOSCI - RETURN CODE 80

Create a new SSA userid to start the LSMGR program, i.e. if a 928 WLOC gateway is used to automatically run VSBIOS (launching LSMGR), change the VATTACH id/password to this newly created id and attempt the operation again. Apparently, some situations such as a system crash, can damage the user profile. Recreating the userid or creating a new profile resets the appropriate operational values.

LSpeed caused an invalid page fault in module lsclient.dll at a memory location 0137: 004541ed

They need to properly shut down Lightspeed. This customer was logging off of Virtual Terminal, but PC Services was still open. Then they would shut down the computer. This would only happen if there was an actual print job passed through the PC Services during the time it was open.

Mailbox name, password or both are missing or are not authorized or is in the wrong format

Check the file handles setting in config.sys.

Max number of files are already open, add FILES=xxx to your CONFIG.SYS - error 4

Increase the number of files handles on the gateway PC.

Maximum sessions already open - error = 100

Update LSVTSERV.

Maximum Subtask Quota too small, change in Security. Unable to invoke Subtask.

Here's the solution for the error "Maximum Subtask Quota too small" working with SCSI g/w's (and 928 too). #1> The User ID that is starting LS should be set to "UNL" for the Subtask Quota. #2> Check the Subtask for LSSERVER within the LS Menu\Utilities\Set SCSI Transport Options (and 928 Transport Options) It should be set to "2". If it was set to the default of 2, then change it to all 0's (zero's) and test again. For this client it fixed the problem going from "6" to "0", but logons/attaches seem to be a little slower. Change it to "2" and see if this helps. Also make sure all the basics are covered, ie...VSbios / VSbiosCI set to have SA rights = YES, protection classes for @lsctrl@ in @system@ and LSconfig in LSdata are set to "blank" and the User ID has UNL for the Subtask Quota.

Message sender not listed in VS directory

The best fix for this situation is to unsync the Lan users from the VS and resync them. You can also correct the users application user ID in wang office using the info from the error message sent back to the sender. You may also use GENAPID to generate the proper check sum.

Missing the (80th column) within VT

What they need to do is run a program called 'VWS' in @system@. Hit the PF1 key to get to the Setup & Configuration screen. The next screen will prompt you to enter a Physical and Logical Unit. Enter the Physical and Logical unit and there should be a Characters Per Line field which defaults to column 79. Increase this number to 80 and now you should see the 80th column when running an IBM or any VS application through VT.

MSMAIL SRV main report following problem - 1

Don't do it. Run DIRSYNC.BAT and the Directory Server or wait till Dispatch runs a scheduled dir sync.

MSMap Error, return code = 092 -- Not enough space on Volume or VTOC

Suggest at least 1000 blocks be free not only for LS data transferring but for their overall VS performance. Make sure the WLOC board is working with the range specified in Vconfig just to make sure that it is working. i.e. WLOC /J=D000.

No system name has been specified for this instance of LS and none can be found in the LS configuration. LS needs to be configured for use on this workstation.

Check the g/w and client's Frame Type - it should be set to Ethernet_802.3 for both the g/w's and client PC's. Do NOT use Ethernet_802.2.

No valid recipients when processing Lan Bound mail. We found a broadcast message in the Queue and deleted it now everything is fine.

This can be caused by a Broadcast message being sent from office. Run GTWMENU and "De-Queue Wang Office Mail"

NTLSPEED hangs

The problem will be fixed by the time that 2.2.0 is released. In the meantime, in the NTLSPEED configuration, please select "Disable Echo Packets." It is the echo (server status, control packet 0x04) that was screwing up. The side effect of disabling these packets is that inactivity time for this gateway in LSMONITR will ramp up when there is no gateway traffic -- it is this server status packet that tells the VS that it is still alive. Disabling it may give operators the impression that their gateway is down when, in fact, it is not. So, be sure to re-enable these packets when 2.2.0 is released. Bryan

Open Process Timeout Errors

Make sure that the program VSBIOS has SSA rights and the user's ID is a System Administrator under SECURITY, also it should have WRITE access from file class A-Z. OPTIONAL: Modify AUTOEXEC.BAT and CONFIG.SYS. Remark out any unnecessary DEVICE drivers in CONFIG.SYS and also remove any unnecessary TSRs in the AUTOEXEC.BAT file. Reboot the PC. Run VSBIOS / VATTACH /S /D and see if it VATTACH's to the VS ok.

Open SPX connection timeout, check maximum data size SP = parameter

Use the /SP switch with Vattach on the client's PC. This will set the SPX packets to the minimum which is around 576 bytes, you can try a higher number......i.e. /SP=1024 or 2048 and test. If the error happens with /SP=2048 but not with /SP=1024, then leave the switch set to /SP=1024. If you use the /SP switch without any value, then the default is 576 -- the minimum setting. Example: Vattach ID pswrd /SP ........etc.

PC hangs during install while displaying "Authoring WP Conversions"

Tweak the memory manager to get more free memory or perform a manual install which is outlined in the back of the manual.

PCI Bus Video Card with WLOC board

The ATI Video card needs the latest PROM upgrade. OLD Revision: 25401-101 NEW Revision: 25408-101. Have the customer check their PROM by visually looking on the card itself. It seems that Gateway has ALL of the OLDER versions of the ATI PROM's for their PCI Video cards, so any new Gateway 2000 586 models WILL have this older Rev PROM. BEWARE! From ATI: Part # for this PROM upgrade is: OFF198 WT PCI ROM 25408-101 NCMAIL. ATI 416-756-0711 tech support # Diamond Computer 408-736-2000 regular # [UPDATE: As of February 1995, ATI is sending out a new VGA card that doesn't have these older problem PROM's installed.]

Print jobs have garbage character(s) in the upper left hand corner of the first page

Here are 2 possible solutions for this: 1.) Run Update Printer Definitions under the LS Menu. (it does it dynamically without stopping the print redirector) 2.) This was a known problem in the LS VS version 3.20.50, PDP32053.zip file fixed this.

Prioritizing Win32 LS traffic via Routers

Correct. LS uses port 1138 for the UDP search of the network for the target or available server and then switches our regular traffic to port 1137 for ongoing TCP traffic. If the router supports selective prioritizing traffic on those ports, then they will achieve the effect of speeding up Lightspeed across their Network, but they will still be limited to any bottlenecks, such as the 928 WLOC adapter.

Processing loop detected

The best way to resolve this loop, if an address in the internal interface object is only used for routing as a default gateway and not being used for inbound source NATing or outbound destination NATing (that is, packets are never destined to this address - only routed through it), is to turn OFF ‘Propagate Packets Destined for this IP Address’ in the address’ properties. With ‘Propagate Packets...' turned ON, a packet destined for this address will be sent to the route object. The route object’s rules dictate that packets destined for the internal subnet be propagated back to the internal interface. The internal interface receives the packet (again) destined for its IP address and then propagates it again to the route object. And so on, and so on, etc. - until it is discarded and reported. Subsequent looped packets are not reported for the sake of the event log. Versions prior to 2.70.00 did properly discard looped packets but did not report the error.

Pseudo blanks are dashes

If the user's have already tried the /P [/G /W] switch(es) on the VSTW command line then try these steps: Changing characters for VSTW using WISCII: 1.) Have the customer Create a WISCII Icon and set the Working Directory to match the "Set LS=" directory. 2.) File\ Open the MSOFTKEY.MAP file [from wherever the "Set LS=" statement is pointing to]. 3.) Preferences\ Select Font [the VSTW font that the customer is using] 4.) Move the cursor bar up to the "0b" line (that's a ZERO) and choose a different character from the bottom of the screen. 5.) File\ Save As the same file, MSOFTKEY.map to the "Set LS=" directory and exit WISCII. 6.) Before starting VSTW, make sure the Working Directory of this Icon is set to the "Set LS=" directory. Also make sure that the user chooses the SAME Font that they just edited from within VSTW to see the changes. That's it, after this is done the dashes should be underscores or whatever character was chosen.

Pseudo blanks are not being copied correctly

Under Manage Configuration, go to VTconfig.lsx and choose the tab "Display", under Fonts, change the default font of lightspeed to something other then a Lightspeed Font.

Return code 2 reported in program MailServ.CPP

Change the setting in the Translation Table Editor to "0" which is default for English. When a number other than zero is placed in this field Mailserv.exe will attempt to located the associated .TRN file which will have the code page properties. If a number is entered in this field and the F10 is not pressed you will never prompted to specify the code page properties and create the .TRN file. NOTE: The information in the error above "Return code 2 reported in program C:\Gtw32\Ecstasy\MailServ.CPP at line number 1516." under LOCATION is reference information for the developer (Nick A.) as to where in his programming environment to find the code creating the error.

Return code R001 from Data Management System OPEN

Map a drive letter to the Volume in file server mode and create a file or directory. This will cause @DOSDIR@ to be created then you can Adopt all orphaned files without errors. NOTE: The file name will be the $Dxxxxxxx VS file name since all the PC information about the file was lost.

Routine DOS_open, path not found

Do not use a UNC path when defining the API Gateway Message Directory and the API Directory Services Directory. Use the local drive mapping path. Example: Use J:\GWISE\WPGATE\API Do not use \\Server1\GWISE\WPGATE\API

Runtime error r6003, integer divide by 0

Increased the environment variable to 1024 and then rebooted the cc:Mail gateway. Right when it started sending mail to the VS, they got the following error: 'Runtime error r6003 integer divide by 0.' Looking through the notes r6003 indicates that its either not enough environment variable or a bad EXE file that is being executed. From the distribution disk, we unzipped CCM_RUN and EXPORT.EXE file and copied the file over to the F:\CCGATE directory. We rebooted the cc:Mail gateway pc and got the same error. The solution for this problem was to run CCM_CFG, go into UTILITIES, and from UTILITIES menu, select INITIALIZE WORKFILES and select INITIALIZE DATABASE FILES. This took care of the runtime error problem. The CC:Mail gateway should now be up and running. When they start up the gateways and start confirmations on mail it reaches a point and they receive an error "run time error r6003 integer divided by 0" (1.14) Added SHELL=C:\COMMAND.COM /P /E:1024 and it's still hung. The gateway was always hanging processing the same confirmation. Initialized the confirmation DBF and all is well.

SCSI chain hangs and inactive LS SCSI Servers

Boot the SCSI g/w PC and go into the CMOS Settings, Disable any Power Management and also any Plug-n-Play options. Also ensure DEVICE=C:\DOS\POWER.EXE is NOT in the Config.sys file.

Service Pack 3 Bugs

There is a Patch for their faulty *.DLL's available from MicroSoft. Once applied, DOS clients can attach to their IP Primary Domains without errors. (ie...Pmonitor g/w's)

Several issues have been fixed on the NT gateway. (2.4.0+)

Both of these issues were fixed by adding a 50 millisecond pause before sending each keystroke to the VS. This also frees the user interface during the attach process. 50ms per keystroke is hardly even a noticeable delay during the attach process. -GPF/Addressing exception if the attach process is canceled when the "retry until successful" option is active and then NTLSPEED is exited. The attach loop had no idea that the attachment had been canceled and would keep trying until attached or until the application was exited. [No customers should have ever reported this problem since they never received this code.] Tom P.

Support for Lower/Upper Case Letters for Print Classes, 26+ ?

The lowercase print classes are not going to be supported at this time (according to Bryan)... They can print to ALL Lightspeed printers by not assigning ANY print class to the printers in the LS Printer Configuration records and assigning SPOOLIB values within Set Usage Constants in Print parameters #PRTxxx; where xxx is the targeted Lightspeed Printer for the client (or print job) AND to assign a common, unused, print class for ALL Lightspeed printing via PRTCLASS in Set Usage Constants or Print job parameters. The print job will reside in the print queue as: FILENAME #PRT123 SYSTEM ABC L 000 The VS will ignore the job because it will not find a valid VS printer number and matching Print class (because the administrator was careful not to duplicate active VS printers and print classes into Lightspeed Printer config records) The Lightspeed Print redirector will recognize the #PRT... entry in the Library field as an indicator that it should direct the print to the printer by the number in the library field (123), search for a match in the Registered printers list and then send the job to that printer. The print class is required because the VS operating system will NOT enter a job into the Print Queue unless a print class is assigned. In this scenario, the print class must not be assigned to either Lightspeed Printers or VS Printers.

SvcDoCommand() rcv'd unsupported command '5'

Use Dos to Unix bridge to edit the file and remove the unused entry

SYMPTOM: Error xx setting current mapped disk drive to X:

FIX: Error 0x15 - Trying to map to a drive letter above or equal to last drive setting. Note Novell login drive is the letter after lastdrive. Error 0x10 - Software is not authorized. Error 0x05 - Redirector is trying to map drive to a drive letter that really exists. Error 0x02 - Not executing on a true MS-DOS compatible operating system. Have seen this reported on a NASCON server and overcame it by moving network drives to G:. I think it was creating some RAM drives to operate from. Additional Messages: Try putting LASTDRIVE = G in your CONFIG.SYS file

The 91st client receives an "Error 121, Timeout has Expired" when trying to attach to a SCSI gateway

Winsocket errors returned when more than 90 (95) users attempt to attach to a SCSI gateway. Lightspeed SCSI gateways are designed to support 128 users per gateway. After researching this issue we have found that although the LS SCSI gateway will support 128 users, Windows 95 Winsocket drivers are unable to allocate the necessary resources to support this many connections. This is not an issue with the Lightspeed Vserver / Wserver programs. The errors that are occurring are happening at the driver level and the connection attempts never make it to our program.

The following files in C:\MSMSTDA.DAT\ were not found or could not be accessed: SPCLMBXS.D01

MAILSERV is trying to access another file SPCLMBXS.D??. If any of these files gets deleted or is missing the MSM2VNS gateway will not run at all. Change to the C:\MSMSTDA.DAT directory and delete any SPCLMBXS.D?? files. These files will get recreated once MAILSERV runs again.

The procedure entry point WNetCachePassword could not be located in the dynamic link library MPR.dll

To fix this problem, copy a version of MAPI32.dll that has been verified as being for Windows NT to the VMT machine. NOTE: To check the version of a MAPI32.dll file, use Explorer to browse the System32 folder under the Windows system directory, do a right-click on MAPI32.dll. From the context menu, pick Properties, then click on the Version tab.

Unable to invoke subtask, return code = 055

Make sure paging is turned on for VS Volume.

Unable to mount device LSR##### and fails with a return code of 12. If the @MCRCU file is release 1.07.7 or later it will fail to bring up Lightspeed SCSI gateways.

It appears that if an earlier version is put in place of the "bad" file the Gateways will respond properly. It is not known what WANG's knowledge of or commitment to correcting this problem is. Side note: Unable to mount device LSR##### and fails with a return code of 12. Found that version 1.07.07 of the @MCRCU Microcode is of too new a version to allow support of our tape device configuration. Customer had to downgrade to version 1.06.06 to get this to work.

Unable to mount device LSR##### and fails with a return code of 12. If the @MCRCU file is release 1.07.7 or later it will fail to bring up Lightspeed SCSI gateways.

The @mcrcu@ file in @system@ must be 1.07.00 or older for our SCSI GW to work, otherwise the LUN 1 channel is not available. We recommend using ver. 1.06.06 of @MCRCU@ in @SYSTEM@. Please be aware: This message ONLY affects customers of CP9 (VS 5000 and 6000) VS systems using the Lightspeed SCSI option and VS/OS version 7.53. NO OTHER SYSTEMS ARE AFFECTED. Version 1.07.02 of the RCU microcode (display the file @MCRCU@ in @SYSTEM@, record 5) no longer supports multiple LUNs (Logical Unit Numbers), a feature on which Lightspeed relies. Multiple LUN support allows several SCSI devices to share the same SCSI ID by using different LUNs. In Lightspeed's case, we mount two 2238V3 tape drives using the same SCSI ID (so that only one SCSI card needs to be installed in the gateway PC) by using LUN 0 and 1. We do not know why multiple LUN support was removed by Wang nor do we know if it will be restored in a future release. Only CP9 (VS 5000 and 6000) systems use RCU microcode.

VATTACH processes successfully; VT or VSTW fails

Assure that WSN (if installed) is started and that Logons are not 'inhibited' - Assure that VSBIOS program (LS library) has SSA rights - Use SECURITY program. - Select PF9 for Program VSBIOS in the LS Library. - Verify "System Administrator = Yes"; change if necessary. - Assure that the LS user id (GW startup ID) has SSA rights -Use SECURITY program. - Select PF1 for userid LS. - Verify "System Administrator = Yes"; change if necessary. - Assure that LS volume is 'Secure' - Use 'Operator Mode' (pf11) from command processor. - Select DISKS (pf10). - Press PF11 (Owner Information). - View 'Secure' column on far right for 'Yes' - if not, set Secure to Yes, then PF10 to change it. - Verify that @LSCTRL@ file in @SYSTEM@ is set as 'Protect Class is BLANK' - Use 'Manage FILES/LIBRARIES' (pf5) from command processor. - Enter the 'SYSTEM' volume name, library name @SYSTEM@, file name @LSCTRL@ and press enter. - Press enter at the @LSCTRL@ file and verify 'Protect Class is BLANK'. - IF IT IS NOT or if you suspect that this file is corrupted.... (This file is used by VSBIOS to access the LSCONFIG file and related components... ALL users must have access to this file to complete processing and connect to the VS) - Go to MENU in LS; select 'Installation'; select 'Set System Options'; note parameters/settings. - Run LSCANCEL to terminate Lightspeed if necessary. - Return to 'Manage FILES/LIBRARIES' (pf5) from command processor. - Enter the 'SYSTEM' volume name, library name @SYSTEM@, file name @LSCTRL@ and press enter. - SCRATCH (PF8) the @LSCTRL@ file. - Return to MENU in LS; Select 'Installation'; Select 'Set System Options'. - Leave Protection Class prompt field blank and press enter. - Reset the parameters and settings according to your notes from above. - Press enter to recreate the 'Control' file. - Restart LS via the Gateways.

Vclient.exe - PC hangs, possible solution (?)

Try inputting the entry just before 'LOCAL=con' at the end of the device list.

Vines Error 163

VMT is designed to access mailboxes through a true Banyan Administrator account. Not a "Nested" list under the AdminList. If a user logging in to Banyan isn't a member of the AdminList itself and instead is a member of an admin list under the AdminList, VMT will not be able to access the mailboxes. The user logging into Vines and running VMT must be added to the AdminList for the server mail is being migrated from.

VS error performing directory sync error code=0, return code=5, extended VS code

Have user get into ???_CFG program and verify exactly what is in those 3 fields. It should only be alphabetic characters! Where ???_CFG is equal to: BAN_CFG or CCM_CFG Also verify that this works: VCOPY <pc_file> E:\volume\library\<work file>

VS printjobs going to another un-specified LS printer

On the VS from the Command Processor, change the SPOOLIB value to "#PRTxxx" in SET USAGE CONSTANTS or use the SET command (SET SPOOLIB = "#PRTxxx") from within their Login Procedure, or they can specify SPOOLIB in customers procedure language. Do NOT specify the PRINTER CLASS from within the Login Procedure. The VS will place the printjob output into the specified SPOOLIB, LS will scan the SPOOLIB's that are prefixed "#PRTxxx" and direct the output to the appropriate LS printer according to the configurations. The SET USAGE CONSTANT value for SPOOLSYS must always be set to blank ( " " ) to accommodate LS printing (printing to PC printers). The SET command parameters can be specified in the user's Login Procedure on the VS as such, i.e. SET SPOOLSYS = " " SPOOLIB = #PRTxxx [xxx=printer number, i.e. 717] Please refer to your VS Procedure Guide / Printing for more details.

VSBIOS 3.20.00 goes into debug

Make sure data encryption is not on. If they must use encryption they can download the fix VSB32001.ZIP which contains VSBIOS, LSINAUTH, VSBIOSCI and LSAUTHSC.

VSBIOS SCSI Transport Location 5001, Error = 0x1388

The LS SCSI g/w has a faulty SCSI adaptor board. Replace it and that should solve this problem. In some cases, the network card is faulty and needs replacing.

VT session failure(s) using Shiva Lan Rover

After much testing, we found that by turning off "PPP Compression" for the modem setup in the Shiva Lan Rover Software, that the VT / VSTW sessions are no longer dropped. A client installation had different modems and some worked without error, but this Compression setting had to be set OFF at the Shiva Router.

VT will try to connect/start the Internet Dialer

The problem is that your TCP/IP stack information is being confused by Network traffic and Internet traffic. To resolve the situation, you must cancel your auto Internet dialer, and start manually dialing into your Internet. This will allow Lightspeed to work just fine. Here are the steps need to accomplish this: 1.) Click on the Start Button 2.) Click on Settings 3.) Click on Control Panel 4.) Double Click the Internet Icon 5.) Go to the tab labeled Connection 6.) Click on the option to "Connect to the Internet using a Local Area Network" or uncheck the box that says "Connect to the Internet as needed". 7.) Click Apply and then close all windows You should now be able to bring up Virtual Terminal without the dial up screen coming up. The problem you may face now is that your Internet is not dialing in. This means you must manually dial in to the Internet first, and then open your browser. If you do not have a Short-cut for your Dialer on your Desktop, please do the following: 1.) Click on Start 2.) Click on Programs 3.) Click on Accessories 4.) Click on Dial-up Networking 5.) Highlight your Dialer Icon for your Internet Provider 6.) Click on File 7.) Click on Create Shortcut 8.) When the window error comes up, choose the option 'YES' to place the short-cut on your Desktop Now when you want to connect to the Internet, double click the Short-cut to your ISP first, and then go into your browser second.

When running the IP Magic Manager or the IP Magic Authorization program: "There was an error communicating with the license service. Please execute the setupex.exe in the directory where the IpMagic Server is installed."

Manually remove cryptkey service and re-install cryptkey service manually. Use the following method: Manual Uninstallation 1. Run SetupEx.exe /d from the IP Magic executables directory (Default is C:\Program Files\Lightspeed Systems\IP Magic). 2. Reboot 3. Delete C:\WINNT\system32\esnecil.ind 4. Delete the following files form the IP Magic executables directory: IpMagic.41s IpMagic.ent IpMagic.key IpMagic.rst Manual Installation Run SetupEx.exe from the IP Magic executables directory (Default is C:\Program Files\Lightspeed Systems\IP Magic). Cryptkey Files C:\WINNT CkConfig.exe - manage the cryptkey server CkConfig.ini - Special zero length file Crypkey.ini - Contains a list of the monitored directories Ckrfresh.exe Setup_ck.dll - Installation helper dll Setup_ck.exe - Installation helper exe C:\WINNT\system32 Crypserv.exe - Cryptkey License Service Ckldrv.sys - NetworkX driver esnecil.ind - License file created the first time Cryptkey is initialized IP Magic Executables Directory SetupEx.exe - Cryptkey installation program. Expands CKS.exe CKS.exe - Self-extracting zip file setupex.xco - Created by SetupEx.exe IpMagic.41s - License file created the first time Cryptkey is initialized IpMagic.ent - License file created the first time Cryptkey is initialized IpMagic.key - License file created the first time Cryptkey is initialized IpMagic.rst - License file created the first time Cryptkey is initialized

When using VSPOOL the printjob goes to the remote VS, but ignores the PRINTCLASS setting and goes to the Class "A" printer

This sounds like a problem described in patch 596 where a remote print job's defaults get set to the users defaults. Suggest check your nucleus file (@sys00x@) and look for string 'RSDP' to see if this patch is loaded. If not, talk to your local Wang people and get it loaded. You may also like to consider moving to 7.50 or 7.52. Just a thought, if you don't have patch 596 you may not have 600 either which is essential for a Lightspeed 7.40.01 VS. It fixes some task crash problems with Lightspeed child tasks. Regards, Neil.

Win32 error: 5 - Access denied

Here's my workaround for this problem: Since the customer does not want to grant all users Admin privileges to the local PC, then they can perform the following registry changes without having to give the user's local Admin rights. We're going to change the permissions so that the user's have access to the Lightspeed program. run <regedt32.exe> (located in the System32 folder)... go to HKEY_LOCAL_MACHINE on Local Machine expand the SOFTWARE folder and the Lightspeed Software folder under Lightspeed Software, highlight the LSNVS folder click on the Security pull-down menu and select Permissions (for LSNVS)... next, click on the Add button and select the user that you want to have access to the Lightspeed program... click on Add again to add the user and then click on OK... highlight the user that you just added and make sure the following boxes are checked... Read Full Control Under Permission make sure that the Allow column have check marks on <Read> and <Full Control> boxes. [9/12/2000 by Danny Quebral]

WP+ printing suspended / WP Plus printing suspended

Be sure that the Lightspeed SARs (System Access Routines) are properly installed and linked. Use the Installation menu to "Display System Access Routine Status". The print redirector must be started by an authorized WP+ user to initiate the WP+ printing. Perform a STOP and START of the Print Redirector using this correct User ID. Validate that WP+ Support has been installed and linked properly during the LS install process by displaying the file LSSERVER in library LS and searching for the text "PDOPEN". The search should return you to a position in the file that reads "PDOPEN RETURN CODE = ", which validates the correct installation and linking of WP+ support. If it is not installed you can run "INSTLWPP" (in the LS library) to install WP+ Print and Document conversion support. Make sure that a necessary library has been created to support WP+ printing. Within WP+ you must create a TEMPDOC library on your System (IPL) volume. If the library resides on a different volume, it must be specified in LS-MENU/VS PRINTING/SPECIAL PRINT OPTIONS/GENERAL PRINT OPTIONS in the TEMPDOC field. Lastly, the target printer must be specified in [WP+] WP ADMIN in CREATE ROUTE PROFILES, using the printer # with a preceding "U". i.e. U125 for LS printer 125 and given a Route name. ************ From our LS VS Manual Gui de:>> If 'WP Plus printing suspended' is displayed, the redirector will not be able to print WP Plus print jobs either. WP Plus printing is suspended if the user who started the print redirector was not given access to the TEMPDOC library in WP Plus or if the print redirector does not have access to the file protection classes used by WP Plus (the default classes are X, Y and Z). There are two ways to give the redirector access to the WP Plus file classes: either the user who starts the redirector must have write access to those classes or the procedure @LSPRT@ protect class can be changed to 'blank'.

WP+ Support needed, without re-installing LS s/w

There is a Proc that will install WP+ if the client happens to answer NO for WP+ Support. It is called INSTLWPP. This can be run on the VS instead of re-installing LS from diskettes again. This process is Not a 100% cure, if it doesn't work then you'll need to reinstall LS from diskettes and answer YES to WP+ Support. Suggested process for this .... run: LSPRTOFF, LSCANCEL, LSREORGB, scratch any Page#### files and the LSMGRMEM file (if present within the LSDATA library) then HALTWP, INSTLWPP, then reIPL the VS, WP / WP+ Support should be installed now.

Wserver hangs when starting WFW

The PC name, Vconfig name and TCP/IP Host name MUST be identical. Also check within Autoexec.bat: WIN C:\LS\WSERVER.EXE /A /L /E=23:50 Note: The WSERVER command should NOT have ANY spaces after the very last character! If it does, it'll give either an Error or just hang.

WW6=xxx is not supported

CCM_RUN must have the following date/time 09/02/95 1.20am

Error in Command Line when trying to invoke Wserver

Go to the properties of the icon for Wserver. Make sure there is no spaces after the last switch on the command line. This is called a "white space" and this will cause the error. i.e. Wserver /A_/L_ is INcorrect, notice the space ' _ ' after the /L. It should be a /L without ANY spaces afterwards.

Error writing to (printer port) for the printer (printer created) the system cannot write to the specified device

Try re-Installing Win95 or WinNT on this 32bit client. Possibly the 32 bit Print Spooler has become corrupted.

Invalid Password using a Wang 724 Keyboard on a Win95 PC

The workaround is to enter the User ID & Password for VT Login under the LSCONFIG.lsx and VTCONFIG.lsx records. They should Attach and Logon, but since the keyboard is not operating properly (shifted mode), you probably won't be able to run any commands because the VS won't recognize the [shifted] characters correctly. Currently in QA for testing.

Issuer: _swapshell. Problem - the program to be executed was not found. Details - attempting to execute REQMAIN. Location - Rtn Code 2 reported in program MSMAILER.cpp @ line 4497, press ESC to exit. (When performing a dirsync)

Check that search mappings and or path statements include the MAILEXE directory.

New Media Player (by MicroSoft) problems with VT

Once you remove the Winsock from the LS directory, VT will come up fine. Explanation: Have you ever used Instant Internet from Bay Networks? It requires it's own Winsock. We've found that you can copy it's Winsock into the Web browser directory and access the Web, leaving the Windows Winsock untouched. This doesn't work with LS and New Media Player.

No job class L" initiator or not enough memory"

Attempting to edit the @LSMGR@ procedure file will be rejected as the file is in the wrong format. Delete or rename the @LSMGR@ file and create a new procedure file with the following lines: 100 Procedure @LSMGR@ 200 LSMGR: Run LSMGR 300 Return code = LSMGR Test the proced