On a workstation - Windows XP - we have a test OE 10.1A db.
If I reboot the box, the AdminService appears to be runing, but ProgressExplorer cannot connect to the server declaring "Cannot connect to the Admin Server. Ensure the Admin Server is running. (8336)" If I go to Services and try to restart the AdminService, I get the message, "The AdminService for OpenEdge 10.1A service on Local Computer started and then stopped." In the Application EventLog, I find an event labeled AdmService_PROGRESS for the start of the AdminService follow by three jvmStart events with the same time stamp and Descritions as follows:
The description for Event ID ( 100 ) in Source ( jvmStart ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: processid 664
The description for Event ID ( 100 ) in Source ( jvmStart ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Successfully started
The description for Event ID ( 100 ) in Source ( jvmStart ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: completed
Then the event showing the AdminService has stopped a second later.
The OA 10.1A db is the only db on the box. It is using the default 20931 port. This problem has come and gone in the past - reboots have from time to time gotten the AdminService talking. Deleting the "server" from ProgressExplorer and putting it back in has sometimes gotten it going. But none of those seem to work anymore.
The db is running, I can connect using the Progress 4GL verdor application. I can query the dB using ODBC. I can go into "Disconnect Users" and see user in the system. Just cannot do ProgressExplorer.
Any ideas?
If I reboot the box, the AdminService appears to be runing, but ProgressExplorer cannot connect to the server declaring "Cannot connect to the Admin Server. Ensure the Admin Server is running. (8336)" If I go to Services and try to restart the AdminService, I get the message, "The AdminService for OpenEdge 10.1A service on Local Computer started and then stopped." In the Application EventLog, I find an event labeled AdmService_PROGRESS for the start of the AdminService follow by three jvmStart events with the same time stamp and Descritions as follows:
The description for Event ID ( 100 ) in Source ( jvmStart ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: processid 664
The description for Event ID ( 100 ) in Source ( jvmStart ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Successfully started
The description for Event ID ( 100 ) in Source ( jvmStart ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: completed
Then the event showing the AdminService has stopped a second later.
The OA 10.1A db is the only db on the box. It is using the default 20931 port. This problem has come and gone in the past - reboots have from time to time gotten the AdminService talking. Deleting the "server" from ProgressExplorer and putting it back in has sometimes gotten it going. But none of those seem to work anymore.
The db is running, I can connect using the Progress 4GL verdor application. I can query the dB using ODBC. I can go into "Disconnect Users" and see user in the system. Just cannot do ProgressExplorer.
Any ideas?