|
This may seem like a dumb question, but did you verify all of your settings in workstation settings for this client? I've seen several times where everything on the server is fine, but someone typed an "O" instead of a 0, etc. The message they receive is: Fatal Error: Cannot Start Physical Server. Error is: Could not start Server Program. (Check INI file) also . . . some of the little C/S spec fields in workstation settings panel don't show the full string you've typed in because they're too small (server config file - AS/400, server path for UNIX). I just helped a client that was having problems because they entered their settings from a co-workers screen print of the settings (which cut off several of the entries). in addition . . . I've seen people have problems if they edit the odo.cfg manually to add a SERVER rather than allowing Session Manager to do this. The problem is that they assume the odo.cfg is used for 1st generation (it is not - ini files in c:\windows are used - these files are not updated by manual additions to the odo.cfg). Hope you get it figured out! +--- | This is the BPCS Users Mailing List! | To submit a new message, send your mail to BPCS-L@midrange.com. | To subscribe to this list send email to BPCS-L-SUB@midrange.com. | To unsubscribe from this list send email to BPCS-L-UNSUB@midrange.com. | Questions should be directed to the list owner: dasmussen@aol.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.