G
Guest
We have a machine running win2000. (Sorry, but I didn't see the Win2000
category listed her anywhere!) It is used as a Goodlink server. (For those
who don't know, Goodlink is an application provided by Sprint to allow for
real time Exchange syncing with Treos.)
The two Goodlink services keep crashing (Goodlink Server and Goodlink
Management Server). The services are setup to Logon As a particular domain
user (an account called GoodAdmin that is only in the Domain Users Group in
AD). Here are the problems -
1.) When the services crash, the Event Viewer shows the one service name
(Goodlink Server service) with a Category = (12) and Event = 1299. There is
one instance of this when the services crash. Then, there will be multiple
(10-20) instances of another Event with the same Category = (12), but with
Event = 1300, all recorded at the exact same time.
The specifics of these Events are -
1299 - Timed operation failed, name:dowork-8 time (ms):1200000, thread
name:dowork-8, thread state:ASolmssen_reqEmailReply, thread id;44144328
1300 - Timed operation failed (list of threads), name:dowork-8 time
(ms):1200000, thread name:main, thread state:MsgWaitForMultipleObjectsEx,
thread id;15055000
2.) When the services crash, they are both set to "Automatic", yet neither
one restarts automatically. And, when we try to manually restart them, we
get the error
"Error 1069: The service did not start due to a logon failure."
So, we have to go into the Properties of the services and retype in the
password on the Log On tab to get the services to restart. Once this is
done, we get the message, something like, "This service has been granted the
"logon as a service" right.
However, in the computer's Local Policy, the domain account used as the log
on account for these services is listed under the "Enable to logon as a
service" entry.
Resetting the password in AD does not help - the password is set to never
expire and is never changed.
Goodlink and Sprint have no clue and have said they think it is an operating
system problem. So, we completely wiped the machine and reinstalled Win 2000
with SP4 and that didn't change anything. Goodlink/Sprint is now saying it
has something to do with our network being bad... We don't believe them.
ANY help would be GREATLY appreciated!!!! Thank you.
Rebecca
category listed her anywhere!) It is used as a Goodlink server. (For those
who don't know, Goodlink is an application provided by Sprint to allow for
real time Exchange syncing with Treos.)
The two Goodlink services keep crashing (Goodlink Server and Goodlink
Management Server). The services are setup to Logon As a particular domain
user (an account called GoodAdmin that is only in the Domain Users Group in
AD). Here are the problems -
1.) When the services crash, the Event Viewer shows the one service name
(Goodlink Server service) with a Category = (12) and Event = 1299. There is
one instance of this when the services crash. Then, there will be multiple
(10-20) instances of another Event with the same Category = (12), but with
Event = 1300, all recorded at the exact same time.
The specifics of these Events are -
1299 - Timed operation failed, name:dowork-8 time (ms):1200000, thread
name:dowork-8, thread state:ASolmssen_reqEmailReply, thread id;44144328
1300 - Timed operation failed (list of threads), name:dowork-8 time
(ms):1200000, thread name:main, thread state:MsgWaitForMultipleObjectsEx,
thread id;15055000
2.) When the services crash, they are both set to "Automatic", yet neither
one restarts automatically. And, when we try to manually restart them, we
get the error
"Error 1069: The service did not start due to a logon failure."
So, we have to go into the Properties of the services and retype in the
password on the Log On tab to get the services to restart. Once this is
done, we get the message, something like, "This service has been granted the
"logon as a service" right.
However, in the computer's Local Policy, the domain account used as the log
on account for these services is listed under the "Enable to logon as a
service" entry.
Resetting the password in AD does not help - the password is set to never
expire and is never changed.
Goodlink and Sprint have no clue and have said they think it is an operating
system problem. So, we completely wiped the machine and reinstalled Win 2000
with SP4 and that didn't change anything. Goodlink/Sprint is now saying it
has something to do with our network being bad... We don't believe them.
ANY help would be GREATLY appreciated!!!! Thank you.
Rebecca