I interpreted "fresh install" as meaning CS-ODBC was not configured. If the system was migrated from an Advanced install which does have CS-ODBC, and the settings were not properly converted in the new server (with service added / running), that could easily be the problem.
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
------------------------------
Original Message:
Sent: 08-02-2019 14:39
From: Doug Higgs
Subject: Cannot print on fresh install
From the PVX PLUS FAQ:
Why am I getting a "Network Communication" error and/or an "ISAM Communication" error?
These errors are typically caused by incorrect settings for the Server Name or IP field and/or the TCP/IP Port field for the Data Source Name (DSN). Check that the network name or IP address and the port are correct. You can verify the port on which the SQL Server is running by looking at the Configuration application (if it is running on Windows) or looking at the pxpsqlsvr.conf file (if it is running on UNIX/Linux).
If these settings are not the issue, then verify there is no network problem and test to see that the server is reachable from the client. You should also verify that firewalls on both the client and the server are not blocking the client or server communication.
------------------------------
Doug Higgs
Assistant Technical Support / Building Maintenance Specialist
Midwest Commerce Solutions, Inc
------------------------------
Original Message:
Sent: 08-02-2019 14:14
From: Randy Marion
Subject: Cannot print on fresh install
The User DSN SOTAMAS90 gets created. I have been playing with it and attempting to test connect to the data but w/o success. I am getting some kind of ISAM errors. Going to try the uninstall/re-install thing again...
------------------------------
Randy Marion
Original Message:
Sent: 08-02-2019 13:59
From: Kevin Moyes
Subject: Cannot print on fresh install
Does SOTAMAS90 get properly created?
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
Original Message:
Sent: 08-02-2019 12:55
From: Randy Marion
Subject: Cannot print on fresh install
I have uninstalled and re-installed as admin and run as admin the first time (did not do this originally) and everyone has full control over workstation folder. Turned UAC off as well. Does not seem to have changed my problem one little bit.
Some background information ... Sage 100 Advanced application server is running on a Win Server 2016 in an AWS environment. We also have setup a Win Server 2016 terminal server in AWS as well that I am attempting to get Sage workstation to run on properly. We have created a domain that both machines belong to. The application seems to be running just fine as long as I do not want to print/preview any reports ... very confused
Randy
------------------------------
Randy Marion
Original Message:
Sent: 08-01-2019 15:30
From: Kevin Moyes
Subject: Cannot print on fresh install
Uninstall, and reinstall As Admin. Run As Admin the first time, making sure you have full control over the workstation folder.
I usually set up servers with UAC off, which bypasses a number of problems.
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON
Original Message:
Sent: 08-01-2019 15:19
From: Randy Marion
Subject: Cannot print on fresh install
@Kevin Moyes - Good idea ... as it turns out, the report does seem to operate when run in Mas90 mode ... Thank you very much... So, how did I screw up the workstation install and how best to fix it?
------------------------------
Randy Marion
Original Message:
Sent: 08-01-2019 15:00
From: Kevin Moyes
Subject: Cannot print on fresh install
If printing works from the back door / MAS90 mode, I'd suspect a bad workstation install / ini.
------------------------------
Kevin Moyes
Technical Systems Analyst
Munjal White Consulting Co.
Toronto ON