We tried restarting the appserver services for the Vanilla environment but still getting the unable to connect “no connection could be made because the target machine actively refused it.” What else can we check to get it up and running? When I did a status check again, the appserver services are hung at a “still starting” status which might be the issue. What else would make it hung at “still starting”?
In our V8 (which used Progress OpenEdge DB), there was a specific order we followed in stopping and starting the DB server and App Servers (“servers” meaning the software instance in Progress, not the physical hardware)
When App Servers would get hung up I’d manually terminate the process using Windows Task Manager, based on the PID (Process ID) displayed in the Progress Explorer Tool (PET).
If you can reset the physical server, that would be best - but I understand if the “Vanilla” DB resides on the same hardware as the live DB.
@ckrusen has covered what I was going to say. In regards to mere troubleshooting. I would check these items.
Is the database instance running?
Is there enough memory for the appserver to spin up the processes/server number assigned? - Each app server has a server setting. This is the number of processes it will spin up to support incoming calls.
If the database server is a different machine can the appserver ping it? - This will cause the appserver instance to hang.
Did you start the appserver software side in the correct order? - I always remember this as shortest appserver name to longest. Epicor905Vanilla, Epicor905VanillaAgent, Epicor905vanillaProcess. I am on E10 now and may not have this accurately named.
Hope this helps!
Do your server logs show more details?
OLD SCHOOL start-up sequence…
(I am not a NASCAS fan, but to get it GOING… STP (as in the auto-stuff)
S = System
T = Task
P = Process
And although your Epi-people would say, you don’t have to wait for each one to get going… it was best on Vantage Progress to do so.
STOPPING… was the opposite P-T-S
How do I know where the database instance is to restart it? Where do I check to see where the Vanilla database is to restart it?
Below are the error logs.
[17/11/30@16:07:51.182-0600] P-005988 T-007964 1 AS – ** Database has the wrong version number. (db: 21845, pro: 21654). (44)
[17/11/30@16:07:51.182-0600] P-005988 T-007964 1 AS – Error initializing the application server. (5479)
[17/11/30@16:07:51.189-0600] P-008132 T-000456 1 AS – ** Database has the wrong version number. (db: 21845, pro: 21654). (44)
[17/11/30@16:07:51.189-0600] P-008132 T-000456 1 AS – Error initializing the application server. (5479)
[17/11/30@16:07:51.189-0600] P-001168 T-007996 1 AS – ** Database has the wrong version number. (db: 21845, pro: 21654). (44)
[17/11/30@16:07:51.189-0600] P-001168 T-007996 1 AS – Error initializing the application server. (5479)
[17/11/30@16:07:51.207-0600] P-004164 T-007988 1 AS – Logging level greater than 1 must be specified either for ASPlumbing or for all types by using -logginglevel. (11072)
[17/11/30@16:07:51.207-0600] P-004164 T-007988 1 AS – Logging level greater than 1 must be specified either for DB.Connects or for all types by using -logginglevel. (11072)
[17/11/30@16:07:51.207-0600] P-004164 T-007988 1 AS – Logging level set to = 1
[17/11/30@16:07:51.207-0600] P-004164 T-007988 1 AS – No entry types are activated
[17/11/30@16:07:51.259-0600] P-006540 T-007468 1 AS – ** Database has the wrong version number. (db: 21845, pro: 21654). (44)
[17/11/30@16:07:51.259-0600] P-006540 T-007468 1 AS – Error initializing the application server. (5479)
[17/11/30@16:07:51.363-0600] P-004164 T-007988 1 AS – ** Database has the wrong version number. (db: 21845, pro: 21654). (44)
[17/11/30@16:07:51.364-0600] P-004164 T-007988 1 AS – Error initializing the application server. (5479)
Is your SQL database a copy of production or a demo database or just the standard? I think this message refers to the progress schema being mismatched. If the database is not a copy of production just run this SQL and compare the two versions (production vs. vanilla). If they match I would assume the placeholders are the culprit.
It should just be the demo database that we got from Epicor as the Vanilla database. Could you provide the SQL query and what do you mean “placeholders”?
Compare this vs. a running version > select * from VntgPatchLevel
A couple things you can check. The first is comparing the OpenEdge Version to one running a current working application server (see screenshot). The second item would be to make sure these files did not get copied over to this folder and instead were properly restored to this folder. What process did you use for creating these?
The OpenEdge version is correct. We have other databases that are running on the same appserver and those get restarted ok.