John Ellis
asked on
App Says Services Are Stopped When They Are Not
Hello:
We have a Windows Server 2008 R2 box with an application on it called Scribe. I have reached out to Scribe, for support, but have been told that this is a networking issue to troubleshoot.
No errors are showing in Event Viewer, and the Scribe app's logs show no errors either.
But, I get these errors shown in the attached Word document upon trying to open the Scribe Console app.
The majority of these errors state that the five Scribe services are not running, even though they are, as shown in the final screenshot of the Word document.
In order to eliminate these errors, I have to manually stop and restart these five services. Although that's simple enough, I should not have to do this just about every day.
And, the Scribe Console is queued to run data import jobs. I have to keep these jobs paused, though. If I don't keep the jobs paused, then restarting these five services will force jobs to run automatically and try to reimport previously imported data into our Microsoft Dynamics GP ERP system.
Does anyone know why an app would say that services are not running, when those services indeed are running?
Thanks! Much appreciated!
John
Scribe-Communication-Link-Errors_Sc.docx
We have a Windows Server 2008 R2 box with an application on it called Scribe. I have reached out to Scribe, for support, but have been told that this is a networking issue to troubleshoot.
No errors are showing in Event Viewer, and the Scribe app's logs show no errors either.
But, I get these errors shown in the attached Word document upon trying to open the Scribe Console app.
The majority of these errors state that the five Scribe services are not running, even though they are, as shown in the final screenshot of the Word document.
In order to eliminate these errors, I have to manually stop and restart these five services. Although that's simple enough, I should not have to do this just about every day.
And, the Scribe Console is queued to run data import jobs. I have to keep these jobs paused, though. If I don't keep the jobs paused, then restarting these five services will force jobs to run automatically and try to reimport previously imported data into our Microsoft Dynamics GP ERP system.
Does anyone know why an app would say that services are not running, when those services indeed are running?
Thanks! Much appreciated!
John
Scribe-Communication-Link-Errors_Sc.docx
ASKER
Thanks, Qlemo! I appreciate the response.
The problem is that we need all jobs to be queued. Otherwise, the Scribe console app serves no purpose.
John
The problem is that we need all jobs to be queued. Otherwise, the Scribe console app serves no purpose.
John
I understood your issue to be that there are old jobs in the queue as soon as the services do not respond, and those are then run after the services are functional again.
If there are jobs queued, and the services work fine, but get restarted to make sure it stays that way, what happens with your jobs and data?
If there are jobs queued, and the services work fine, but get restarted to make sure it stays that way, what happens with your jobs and data?
ASKER
When the services are restarted, the jobs pull files of data that was already imported.
Why? That should be the same if you restart the server ... unless the non-responsive services are causing that behaviour, and then it will not happen if the services are restarted in time.
ASKER
Hi Qlemo:
This error is preventing me from opening the Console to unpause the jobs. And, if this server ever gets this Communication Link Failure error, then--whether I can open the Console or not)--anyunpaused jobs will essentially re-run (i.e. try to pull in data that has been previously imported).
John
This error is preventing me from opening the Console to unpause the jobs. And, if this server ever gets this Communication Link Failure error, then--whether I can open the Console or not)--anyunpaused jobs will essentially re-run (i.e. try to pull in data that has been previously imported).
John
We are at square one again. You just confirm that the workaround is to act before the services connections get refused! If you manage to restart the services more often and at a time they certainly still run well, it should work.
The better option is to get the Scribe folks fixing this issue. Don't allow for excuses. They need to at least tell you what is causing the failure, if not able to fix.
The better option is to get the Scribe folks fixing this issue. Don't allow for excuses. They need to at least tell you what is causing the failure, if not able to fix.
ASKER
Let's say that I open the Console and enable all jobs. That's what we want.
Further, let's say that I somehow "time" these services to start and restart on their own so that the Communication Link Failure error does not happen.
(I have seen this Communication Link Failure error come about on its own, in the middle of the night, because the server in the past has sent me an e-mail to that effect.)
When the Communication Link Failure error happens, the only solution that I'm being given by Scribe is stop and restart services.
But, if the services stop and restart while all jobs are enabled, then the jobs will run and try to reimport previously imported data.
This is the crux of the issue.
John
Further, let's say that I somehow "time" these services to start and restart on their own so that the Communication Link Failure error does not happen.
(I have seen this Communication Link Failure error come about on its own, in the middle of the night, because the server in the past has sent me an e-mail to that effect.)
When the Communication Link Failure error happens, the only solution that I'm being given by Scribe is stop and restart services.
But, if the services stop and restart while all jobs are enabled, then the jobs will run and try to reimport previously imported data.
This is the crux of the issue.
John
Understood. But what do you expect us to say or do, beyond what I posted already?
Do you think it is possible to find a schedule for restarting services? If so, a scheduled task running following batch file (.cmd) should do (with correct service names, of course):
Do you think it is possible to find a schedule for restarting services? If so, a scheduled task running following batch file (.cmd) should do (with correct service names, of course):
net stop svc1
net stop svc2
ping -n 6 127.0.0.1 >nul
net start svc2
net start svc1ASKER
Hi Qlemo:
Thanks, for your response! I apologize, for the delay in getting back to you.
You were asking, "But what do you expect us to say or do, beyond what I posted already?".
I was simply expanding on the problem, to make sure that I was clear.
I'm afraid that scheduling the restarting of services is not an option. :(
John
Thanks, for your response! I apologize, for the delay in getting back to you.
You were asking, "But what do you expect us to say or do, beyond what I posted already?".
I was simply expanding on the problem, to make sure that I was clear.
I'm afraid that scheduling the restarting of services is not an option. :(
John
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Qlemo:
The problem is that, before having the services restart, I have to pause the Scribe import jobs.
My IT department is going to try disabling the TCP Chimney Offset feature to see if that eliminates the Communication Link Failure error that forces a restart of the services.
Thanks, for your help! It's appreciated!
John
The problem is that, before having the services restart, I have to pause the Scribe import jobs.
My IT department is going to try disabling the TCP Chimney Offset feature to see if that eliminates the Communication Link Failure error that forces a restart of the services.
Thanks, for your help! It's appreciated!
John
The Chimney feature has been an issue on Vista, but had been fixed in W7 (and W2008r2), and I didn't hear from issues caused since then. But it might be worth a try, despite my doubts.
There seems to be no Scribe Expert on EE, so we are bound to guessing or trial and error. There might be no way to pause the jobs by a script.
There seems to be no Scribe Expert on EE, so we are bound to guessing or trial and error. There might be no way to pause the jobs by a script.
- The service state as displayed by the Service Manager. This only tells that the executable runs and reports back to the Service Manager, so seems to be alive.
- The internal communication state of the services. The services might run, but not take any input anymore.
The error messages shown tell that the (TCP?) connections do not work anymore. That hints towards running services without doing anything anymore.Best you probably can do without knowing the cause is to regularly restart all services on schedule, say each noon, while you are certain there are no queued jobs.
I do not agree to the Scribe support statement. This is a "service stopped to respond" issue, no network issue. It might be OS related, but it is still an issue with the specific services.