HELP! Service Specific Error 4017
Graham Fountain
start - it is giving an error 4017. I have searched the Microsoft Knowledge
Base on this error code and got nothing. I have run the eseutil program on
the databases - it found no errors and still the problem persists. I have
tried the isinteg utility also.
When rebooted, the only exchange service that automatically starts is the
system attendant. The event viewer says
"The Microsoft Exchange Information Store Service depends on the Microsoft
Exchange Directory Service which failed to start because of the following
error: The operation completed successfully"
The Message Transfer Agent also reports the same error.
Once booted I can manually start the Directory Service and the Message
Transfer Agent with no errors. But when I manually start the Information
Store I get the error 4017.
What is error 4017? I found an error 4018 that was documented as being a
problem with file permissions.
Thanx in advance for any help anyone can provide.
Kirill S. Palagin
Graham Fountain wrote:
--
Questions will not be answered via e-mail.
Graham Fountain
Kirill S. Palagin <kpalagin@phxint.-nomailplease-glasnet.ru> wrote in
message news:37A19F46.526B398F@phxint.-nomailplease-glasnet.ru...
> So why Directory service does not want to start?
I have absolutely no idea why it doesn't start at bootup. There is
absolutely nothing in the event viewer about Directory Service not starting,
except for the stupid message given by the Information Store and Message
Transfer Agent that the Directory Service didn't start because the operation
completed successfully. As I mentioned previously, Directory Service does
start if I start it manually.
Graham Fountain
BTW, I think I forgot to mention, I am running Exchange 5.5 SP2
Even though the eseutil & isinteg functions didn't find anything wrong, I
restored from a backup and then the Information Store gave an error 1011,
which according to MS is normal after restoring a backup. I ran the
isinteg -patch as suggested on the MS Knowledge Base, and presto! Back to
error 4017.
One thing I did notice after restoring from the backup, isinteg is giving a
warning that the Private Information Store could not be found. Is this part
of the problem?
The eseutil command when run with /g /ispriv has no problem locating the
private information store - don't they both pick it up from the registry?
In desperation, thinking that it could be a permissions problem, I have made
the entire exchsrvr directory tree world readable and writable, and still no
difference.
Rich Matheisen
>Some more information on the problem.
>
>BTW, I think I forgot to mention, I am running Exchange 5.5 SP2
>
>Even though the eseutil & isinteg functions didn't find anything wrong, I
>restored from a backup and then the Information Store gave an error 1011,
>which according to MS is normal after restoring a backup. I ran the
>isinteg -patch as suggested on the MS Knowledge Base, and presto! Back to
>error 4017.
Is that an ERROR 4017 or is that the EventID of what yu're looking at
in the Applications Log?
Tell us the Event ID, Source, Category, Type, and Description of that
Event.
>One thing I did notice after restoring from the backup, isinteg is giving a
>warning that the Private Information Store could not be found. Is this part
>of the problem?
Well, it certainly isn't a GOOD sign!
It could mean the IS is dmaged in a way that makes it unusable.
>The eseutil command when run with /g /ispriv has no problem locating the
>private information store - don't they both pick it up from the registry?
Sure, but they deal with the file in different ways. ESEUTIL deals
with the file itself and not with the database within it. ISINTEG
deals only with the organization of the database, its tables, indexes,
etc.
>In desperation, thinking that it could be a permissions problem, I have made
>the entire exchsrvr directory tree world readable and writable, and still no
>difference.
Permissions aren't a problem. Try this: MOVE everything in the MDBDATA
directories EXCEPT the PRIV.EDB and PUB.EDB to another directory (you
may have more than ne MDBDATA directory!). Then run ESEUTIL /R /ISPRIV
and ESEUTIL /R /ISPUB. Then run "ESEUTIL /MH
x:\exchsrvr\mdbdata\priv.edb" and "ESEUTIL /MH
x:\exchsrvr\mdbdata\pub.edb" and verify that they are both in a
consistent state. If they are, try starting the IS.
------------------
Rich Matheisen
MCSE, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm
Graham Fountain
Rich Matheisen <r.mat...@worldnet.att.net.NOSPAM.COM> wrote in message
news:37b847f8...@msnews.microsoft.com...
<snip>
> Is that an ERROR 4017 or is that the EventID of what yu're looking at
> in the Applications Log?
>
> Tell us the Event ID, Source, Category, Type, and Description of that
> Event.
When I start it manually It just pops up a window stating that it couldn't
start the service because it returned Service Specific Error 4017. The
event viewer has:
Event Id: 7024
Source: Service Control Manager
Type: Error
Category: None
"The Microsoft Exchange Information Store Service terminated with
service-specific error 4017.
When it fails to start at bootup the error in the event viewer is that it
failed because the Directory Service failed to start.
Event Id: 7001
Source: Service Control Manager
Type: Error
Category: None
"The Microsoft Exchange Information Store Service depends on the Microsoft
Exchange Directory Service which failed to start because of the following
error:
The Operation Completed Successfully"
There are no events as to why the Directory Service didn't start.
I have also tried restoring from a one-week old backup that was made at the
file level with the exchange services disabled. It still gives the 4017
error, but doesn't give the 1011 error, like I get when I restore the
exchange database from tape.
>
> >One thing I did notice after restoring from the backup, isinteg is giving
a
> >warning that the Private Information Store could not be found. Is this
part
> >of the problem?
>
> Well, it certainly isn't a GOOD sign!
Didn't think it would be, the wierd bit is that isinteg -pri works, but
isinteg -patch gives this error.
<snip>
> Permissions aren't a problem. Try this: MOVE everything in the MDBDATA
> directories EXCEPT the PRIV.EDB and PUB.EDB to another directory (you
> may have more than ne MDBDATA directory!). Then run ESEUTIL /R /ISPRIV
> and ESEUTIL /R /ISPUB. Then run "ESEUTIL /MH
> x:\exchsrvr\mdbdata\priv.edb" and "ESEUTIL /MH
> x:\exchsrvr\mdbdata\pub.edb" and verify that they are both in a
> consistent state. If they are, try starting the IS.
I'll give this a go and post my results.
root
> Rich Matheisen <r.mat...@worldnet.att.net.NOSPAM.COM> wrote in message
> news:37b847f8...@msnews.microsoft.com...
> <snip>
>> directories EXCEPT the PRIV.EDB and PUB.EDB to another directory (you
>> may have more than ne MDBDATA directory!). Then run ESEUTIL /R /ISPRIV
>> and ESEUTIL /R /ISPUB. Then run "ESEUTIL /MH
>> x:\exchsrvr\mdbdata\priv.edb" and "ESEUTIL /MH
>> x:\exchsrvr\mdbdata\pub.edb" and verify that they are both in a
>> consistent state. If they are, try starting the IS.
> I'll give this a go and post my results.
Tried this, no more error 4017, now the information store just sits
for ages when I try to start it and after a while I get the error
that it wasn't responding to the control request. I'm not at work
anymore, so I can't give the exact message it gave.
I've all but given up on this now. My next step is to put NT &
Exchange on a new machine. Once this is working, I'll try copying the
EDB files over and see if I can get anything out of them on the new
machine. I am starting to wonder if it is a hardware problem, or some
registry setting that is causing the problem.
If I can't get the data from the new machine then I think it is about
time to bid our old data farewell and start fresh. The thing that really
has me stumped though is that even when restoring from backups it won't
work - it nearly _has_ to be something other than the data files that is
at fault.
Kirill S. Palagin
When you trying to start Directory Service, do you get any relevant events in NT
App Event log?
Graham Fountain wrote:
<snip>
Graham Fountain
Kirill S. Palagin <kpalagin@phxint.-nomail0please-glasnet.ru> wrote in
message news:37A27688.290DBB3@phxint.-nomail0please-glasnet.ru...
>
> When you trying to start Directory Service, do you get any relevant events
in NT
> App Event log?
that it won't load at boot up, but gives no reasons why, but will load
manually.
Kirill S. Palagin
What happens if (after that) you start MSExchangeIS?
Graham Fountain wrote:
> Kirill S. Palagin <kpalagin@phxint.-nomail0please-glasnet.ru> wrote in
> message news:37A27688.290DBB3@phxint.-nomail0please-glasnet.ru...
> >
> > When you trying to start Directory Service, do you get any relevant events
> in NT
> > App Event log?
> Not a thing in either the app or the system log. It just doesn't make sense
> that it won't load at boot up, but gives no reasons why,
I would say that it must complain about something, but if are saying this ... .
Graham Fountain
the priv.edb or pub.edb files.
I have an exchange server working again now. What I ended up doing was
fitting a new hard disk in to the server, went through the tedious process
of installing SBS 4.0 and upgrading to SBS 4.5. I now had a working MS
Exchange Server, so I copied the pub.edb and priv.edb files from the
original hard disk.
At first it didn't want to work but after running eseutil /p /ispriv and
eseutil /p /ispub and then isinteg -patch, everything started up and
operated as it should - apparently with all data intact. Now I'm going
through the process of getting all our other software and functions back on
to the "new" NT server.
I still have no idea what caused the error 4017, but I am fairly sure it has
to be because of an incorrect registry setting on the computer, considering
I completely recopied the exchsrvr directory without success. It's working
now so I don't care what caused it - as long as it doesn't happen to me
again :-)
One thing I discovered during the course of this: The Internet Mail
connector refused to start until I had created a setting in the Dial Up
Networking. Even though we have a LAN connection to the internet, it needed
this Dial Up Networking entry to load. As far as I can tell, Internet Mail
isn't set up to use the modem. I don't know if this is documented, but it
took me a good 10 minutes of mucking around until I twigged what the problem
was.
Graham Fountain <gra...@myall.net> wrote in message
news:crfo3.36$Qg1....@nsw.nnrp.telstra.net...
> I have a problem with my exchange server - the information store refuses
to
> start - it is giving an error 4017. I have searched the Microsoft
Knowledge
> Base on this error code and got nothing. I have run the eseutil program
on
> the databases - it found no errors and still the problem persists. I have
> tried the isinteg utility also.
>
> When rebooted, the only exchange service that automatically starts is the
> system attendant. The event viewer says
>
> "The Microsoft Exchange Information Store Service depends on the Microsoft
> Exchange Directory Service which failed to start because of the following
Graham Fountain
> So you can get MSExchangeDS running?
> What happens if (after that) you start MSExchangeIS?
Matheison I deleted all other files in the mdbdata directory except priv.edb
and pub.edb. Then ran the eseutil on them. Now it doesn't give error
4017 - just pauses for _ages_ and says that the service didn't respond to
the control request. I'm not at work so I can't remember the exact message.
I am starting to think this is a registry problem, not a database problem,
because even after copying the entire exchsrvr directory from a backup made
nearly a week ago (the backup was made with a hard disk cloning program
doing a sector by sector copy of the drive) the error 4017 still persists.
I haven't tried restoring from this backup since I started getting the error
about it not responding to the control request, will do that Monday. Also
my next line of attack is to install NT and Exchange on another machine, and
then try copying the EDB files to that machine. At the very least, this
should isolate if it is a database problem or some other problem with the
server. I was going to uninstall and reinstall exchange server, but it is
SBS 4.5, and I can't convince the setup program that it should uninstall
anything.
In a previous post, I gave the error messages that are coming up in the log,
I will repost them here in case you missed that post. (again this is from
the error 4017, I don't have access to the machine again until Monday so I
can't give you the messages from the current error).
When I start it manually It just pops up a window stating that it couldn't
start the service because it returned Service Specific Error 4017. The
event viewer has:
Event Id: 7024
Source: Service Control Manager
Type: Error
Category: None
"The Microsoft Exchange Information Store Service terminated with
service-specific error 4017.
When it fails to start at bootup the error in the event viewer is that it
failed because the Directory Service failed to start.
Event Id: 7001
Source: Service Control Manager
Type: Error
Category: None
"The Microsoft Exchange Information Store Service depends on the Microsoft
Exchange Directory Service which failed to start because of the following
error:
Rich Matheisen
>> Is that an ERROR 4017 or is that the EventID of what yu're looking at
>> in the Applications Log?
>>
>> Tell us the Event ID, Source, Category, Type, and Description of that
>> Event.
>
>When I start it manually It just pops up a window stating that it couldn't
>start the service because it returned Service Specific Error 4017. The
>event viewer has:
>Event Id: 7024
>Source: Service Control Manager
>Type: Error
>Category: None
>"The Microsoft Exchange Information Store Service terminated with
>service-specific error 4017.
>
>When it fails to start at bootup the error in the event viewer is that it
>failed because the Directory Service failed to start.
>Event Id: 7001
>Source: Service Control Manager
>Type: Error
>Category: None
>"The Microsoft Exchange Information Store Service depends on the Microsoft
>Exchange Directory Service which failed to start because of the following
>error:
>The Operation Completed Successfully"
>
>There are no events as to why the Directory Service didn't start.
That may be, but I'm going to hazard a guess and say that it's not the
IS that's the cause of your problem. I'd suspect the directory. The
error 4017 is right in the range of 4015 - 4021 and that seems t
_imply_ the same sort of problem might be the cause of the 4017.
Since you can start the directory service manually, I'd suggest that
you try the course of action laid out in the MS KB article:
Q162353 "XADM: Restoring an Exchange Directory"
You'll be able to salvage the mailboxes, custom recipients, and
mailboxes from the directory by constructing the necessary CSV header
(if you need to export more than the default set of properties from
the objects). If my suspicion is correct the IS is okay and you'll be
able to use it after importing the CSV into the new directory.
I wouldn't delete the old directory, though. Before you remove
Exchange from the server, make a copy of the DIR.EDB and all the log
and chk files. You never know when you might need something in it that
you forgot! Just keep it around until you're satisfied that all the
info you need is in the new directory.
Remember, this is based on *intuition* and NOT on FACT! A call to MS
PSS might be in order if you don't feel comfortable with this
approach!
Rich Matheisen
>As I suspected, this fault is something more than a database corruption in
>the priv.edb or pub.edb files.
>
>I have an exchange server working again now. What I ended up doing was
>fitting a new hard disk in to the server, went through the tedious process
>of installing SBS 4.0 and upgrading to SBS 4.5. I now had a working MS
>Exchange Server, so I copied the pub.edb and priv.edb files from the
>original hard disk.
>
>At first it didn't want to work but after running eseutil /p /ispriv and
>eseutil /p /ispub and then isinteg -patch, everything started up and
>operated as it should - apparently with all data intact. Now I'm going
>through the process of getting all our other software and functions back on
>to the "new" NT server.
You're missing a great deal of information in the directory. Running a
DS/IS Consistency Adjustment will repopulate the directory for you.
What you did confirms what I said about the problem being the
directory and not the information store.
>I still have no idea what caused the error 4017, but I am fairly sure it has
>to be because of an incorrect registry setting on the computer, considering
>I completely recopied the exchsrvr directory without success. It's working
>now so I don't care what caused it - as long as it doesn't happen to me
>again :-)
Copied it from where? And was it any good when it was copied?
>One thing I discovered during the course of this: The Internet Mail
>connector refused to start until I had created a setting in the Dial Up
>Networking. Even though we have a LAN connection to the internet, it needed
>this Dial Up Networking entry to load. As far as I can tell, Internet Mail
>isn't set up to use the modem. I don't know if this is documented, but it
>took me a good 10 minutes of mucking around until I twigged what the problem
>was.
If this is true then it's restricted to SBS. The "normal" Exchange
server doesn't require any Dial-UP Networking information to function.
Graham Fountain
<snip>
> Copied it from where? And was it any good when it was copied?
the hard disk with Norton Ghost. The system had been booted from a DOS
floppy. I copied the entire exchsrvr directory from this drive back to the
main server drive, and it still wouldn't run - just gave error 4017. This
would have restored the Directory and Information Store, and would have
corrected any defects in the applications if any. I think that having done
this without success indicates to me that there must have been a registry
setting (or a DLL somewhere else on the drive?) that was at fault.
As soon as I started having the problem I backed up the "faulty" exchsrvr
directory as well. It was with this "faulty" data that I got the server
back up and running with after it was reinstalled on a fresh drive. (I only
copied the pub.edb and priv.edb files - I didn't want to risk it just in
case it is the directory that is at fault). I admit that this doesn't
isolate the possibility of a fault in the directory, but I think the
previous efforts involving copying from a known good backup prove that the
fault wasn't in the directory.