Sage 100

Sage 100 Advanced through Terminal Server. Customer gets this error this morning: ""ProvideX:Startup Error #100 - No driver for terminal type or library missing"" The Sage KB article isn't clear to me. Is this a ws reinstall? We just reinstalled it last night.

My first guess would be user rights though the IT people will deny it for several days until they relent and find that just maybe it was rights all along. Here's the PVX error description: No driver for terminal type or library missing During initialization PxPlus could not locate the device driver module for the type of terminal you are using (as defined in the TERM environment variable). This error may also result because the system cannot find the PxPlus library.

Thanks Wayne. Luckily we have very good relations with IT on this, and IT has significant MAS experience. It was rights and a bit more. In this case IT had previously (and correctly) installed client on TS. This is a relative new customer for us, and we hadn't yet had to do any installation work. Then last evening Chuck uninstalled and reinstalled the client to fix a PDF dll issue. It ran fine. Of course our login has Administrator rights, so we didn't see the issue that users saw first thing in the morning. It would have been ok except that we'd reinstalled the client to the standard c:\ location, not the odd place that IT had originally used. That also created a wave of issues because of (clever) way IT had set up shortcuts. I think the lesson is that when you first re-install in and environment you did not set up, especially on TS, at the very least log back in as NON-Administrator to check the job.

good suggestion on the login test

The other issues I've run into are the activex.pvx file not copying correctly, so have to manually copy it to the terminal server. Our usual practice is to make a copy of the activate.pvx so we can copy it while Sage 100 is running.. The other issue I've run into is that I had to go back to the MAS90 folder on the terminal server and change the permissions on it so everyone had full rights. I don't know if these are due to my errors when installing, but I've had to do it multiple times at one client.