SQLDUMPER library error message (PLEASE HELP)

[Guest]

Every time I boot my XP Pro SP2 laptop I get an error message that the
"SQLDUMPER library did not initialize or is corrupt..." and instructed to
"...run setup and reinstall..." This error message began to appear after I
uninstalled Windows Accounting 2007.

Does anyone know what this means and/or what I should do to correct the
problem?

(e-mail address removed)

 

[db]

you might try to
run "eusing registry
cleaner" and see if
the issue is related
to an orphaned registry
key...

- db
Every time I boot my XP Pro SP2 laptop I get an error message that the
"SQLDUMPER library did not initialize or is corrupt..." and instructed to
"...run setup and reinstall..." This error message began to appear after I
uninstalled Windows Accounting 2007.

Does anyone know what this means and/or what I should do to correct the
problem?

(e-mail address removed)

 

[Guest]

Thanks db, but what is the "eusing registry cleaner"?

 

[db]

here is the link where you
can get it and more info as well:

http://www.eusing.com/free_registry_cleaner/registry_cleaner.htm
Thanks db, but what is the "eusing registry cleaner"?

 

[Guest]

Found it and ran it: It found 707 "problems" and "repaired" them. My system
seems a little peppier now but I still get the "SQLDUMPER library does not
initialize..." Any idea what it is and how one might go about reinstalling
it? THANKS for trying to help.

 

[Guest]

Hi Gene,
Try to start with clean boot and uncheck the line from start up for the
application (Windows Accounting 2007) from starting up.
To do that do this:
Open a run command and type in:
msconfig click [OK] on the System Configuration click on StartUp Tap and
uncheck the line as mention for the windows accounting 2007 and the SQLDUMPER.

Reboot and see if you will get the error, does it appear?.
If yes, then open a run command and type in:
sfc /scannow click [OK] and wait for it to finish, then Run Disk CleanUp
and Reboot.
HTH.
Let us know.
nass

 

[db]

i'm glad it gave your system
some pep but disappointed
that the issue you have may
not be an orphaned registry key.

i base this on the fact that
if a system restore point was
made prior to installing the
accounting software, then
that restore point could have
been used to bring your system
back to the way it was before
installing the accounting software.

this is still an option available
and possibly the freeware did
not recognize this particular
key.

however, it's likely that the two
suggestions that nass provided
can resolve the issue as well.

let us know...

Found it and ran it: It found 707 "problems" and "repaired" them. My system
seems a little peppier now but I still get the "SQLDUMPER library does not
initialize..." Any idea what it is and how one might go about reinstalling
it? THANKS for trying to help.

 

[Rock]

Found it and ran it: It found 707 "problems" and "repaired" them. My
system
seems a little peppier now but I still get the "SQLDUMPER library does not
initialize..." Any idea what it is and how one might go about reinstalling
it? THANKS for trying to help.

I'm glad you aren't seeing any immediate problems from using a registry
cleaner, nor does it surprise me that running it didn't fix your problem
There are two sides to the issue of using one, so let me state my side.

You should not use a registry cleaner. There is generally no advantage to
cleaning the registry, but problems can occur as a result of using one.
Unused entries in the registry do not, in general, cause problems. If there
is a problem that is associated with an entry in the registry the way to
deal with this is to manually edit the registry. When using an automated
registry cleaner, you're at the whim of the program as it decides what is
not needed; unfortunately the problem is it can remove something that is
needed at some time later, and then suddenly for what appears to be no
apparent reason, a problem surfaces.

Different cleaners will differ in how aggressive they are in making
suggestions on what to remove, but the basic fact is that removing orphaned
entries doesn't do much. It's a mental placebo.

I suggest if that program has a undo feature you use it. The only way to
use a registry cleaner is for suggestions on what needs to be changed, which
you should research to see if those changes are needed, and make changes one
or just a few at a time.

As to your issue, who is the author for Windows Accounting 2007? Is that
the software name? You could contact their tech support for info . Also
you could do some reading in these links:

http://www.google.com/search?hl=en&q=SQLDUMPER+library+does+not+initialize+or+is+corrupt

 

[db]

unfortunately, you know it's one thing
to express a contradiction
based on a lack of experience.

however it is another to contradict
the experts who have been
creating registry cleaners for
their o.s.'s and the hand that
feeds your ego.

You know them as Microsoft
as in Microsoft MVP and
Windows as in the operating
system that you profess to
be experienced with.

the statement you provided
regarding the registry is
inaccurate and directly
contradicts this:

http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm

what's so disturbing is
that your fellow MVP's may
not be providing you with
guidance and education
that can.....

honestly, if you are actually
a Microsoft MVP you should
be providing support for
their software like Microsoft's OneCare

Found it and ran it: It found 707 "problems" and "repaired" them. My
system
seems a little peppier now but I still get the "SQLDUMPER library does not
initialize..." Any idea what it is and how one might go about reinstalling
it? THANKS for trying to help.

I'm glad you aren't seeing any immediate problems from using a registry
cleaner, nor does it surprise me that running it didn't fix your problem
There are two sides to the issue of using one, so let me state my side.

You should not use a registry cleaner. There is generally no advantage to
cleaning the registry, but problems can occur as a result of using one.
Unused entries in the registry do not, in general, cause problems. If there
is a problem that is associated with an entry in the registry the way to
deal with this is to manually edit the registry. When using an automated
registry cleaner, you're at the whim of the program as it decides what is
not needed; unfortunately the problem is it can remove something that is
needed at some time later, and then suddenly for what appears to be no
apparent reason, a problem surfaces.

Different cleaners will differ in how aggressive they are in making
suggestions on what to remove, but the basic fact is that removing orphaned
entries doesn't do much. It's a mental placebo.

I suggest if that program has a undo feature you use it. The only way to
use a registry cleaner is for suggestions on what needs to be changed, which
you should research to see if those changes are needed, and make changes one
or just a few at a time.

As to your issue, who is the author for Windows Accounting 2007? Is that
the software name? You could contact their tech support for info . Also
you could do some reading in these links:

http://www.google.com/search?hl=en&q=SQLDUMPER+library+does+not+initialize+or+is+corrupt

 

[Guest]

OK guys, I've done it all and still get the error message. I also went to
the SQL forum recommended by Rock and posted this message:

I have the exact same problem running Windows XP Pro/SP2, and would like to
fix it. Surly someone here must know how to do it. Here's what I've done so
far w/ no help:

--I ran eusing registry cleaner and "fixed" 707 problems
--I ran msconfig and could find nothing like SQLDUMPER in the Startup lines
to uncheck
--Then I ran sfc /scannow followed by Disk CleanUp w/ no change

A couple other things: 1. The problem started after I uninstalled Microsoft
Accounting 2007, a new program that I do not even know when or why I
downloaded to my computer. It may be purely coincidental, but that is when it
started. I'd go back to a Restore Point, but I don't know when installed the
software. 2. The error message ends w/ this "...Please uninstall then re-run
setup to correct this problem." The problem is I do not know what to
uninstall or what setup to re-run.

PLEASE HELP...

Any other ideas?

 

[Malke]

db wrote:

(snip another unreadable post)

I hardly think that a person such as yourself who isn't able to fix his
own posting line length is qualified to provide computer tech support or
an opinion on using registry cleaners.

Malke

 

[Malke]

OK guys, I've done it all and still get the error message. I also went to
the SQL forum recommended by Rock and posted this message:

I have the exact same problem running Windows XP Pro/SP2, and would like to
fix it. Surly someone here must know how to do it. Here's what I've done so
far w/ no help:

--I ran eusing registry cleaner and "fixed" 707 problems
--I ran msconfig and could find nothing like SQLDUMPER in the Startup lines
to uncheck
--Then I ran sfc /scannow followed by Disk CleanUp w/ no change

A couple other things: 1. The problem started after I uninstalled Microsoft
Accounting 2007, a new program that I do not even know when or why I
downloaded to my computer. It may be purely coincidental, but that is when it
started. I'd go back to a Restore Point, but I don't know when installed the
software. 2. The error message ends w/ this "...Please uninstall then re-run
setup to correct this problem." The problem is I do not know what to
uninstall or what setup to re-run.

Registry cleaners are dangerous in unskilled hands and in any case would
not help with your error. You need to either contact Microsoft
Accounting 2007 tech support - and this could not have magically
installed by itself, you must have installed it with something - perhaps
an MS Office 2007 trial - or do a System Restore.

You will be able to tell which System Restore point to restore to be
looking at them. When you highlight the dates in bold on the System
Restore calendar on the left, look on the right panel. This will say
what happened. If you are fortunate, you'll see an entry made just
before you installed MS Accounting. That's the restore point you want.
If you are unfortunate and can't find such an entry, then surely you
remember roughly when you installed this new program. Pick a date before
that with the understanding that going back more than a few weeks isn't
a good idea.

I also doubt that you would see an entry in msconfig for SQLDUMPER since
this is only produced when there is an error in whatever is using SQL.
You should be looking for something Office-related that is set to start
with Windows.

You might also see if there is a SQL service running and temporarily
disable it. This is only useful and safe if you have no other programs
using SQL. If you are a home user, you probably don't. To do this:

Start>Run>services.msc [enter]

Scroll down until you see the correct SQL entry, double-click it, stop
the service and set it to disabled.

Here is the homepage for Microsoft Office Accounting Professional:
http://office.microsoft.com/en-us/accounting/default.aspx


Malke

 

[db]

i apologize for the castigation
of an earlier email, but it gets
somewhat frustrating trying to
help resolve issues on the frontpage
and on the backpage as well.

i do have a few more
ideas. But it would be more
helpful to you/us to get that
specific error addressed
directly at:

http://www.microsoft.com/office/com...dg=microsoft.public.sba.general&lang=en&cr=US

or here


the experts hang around the above and
have likely encountered a similar issue
like yours. It seems reasonable that this
is a bug in the program and not your o.s.

so my attempts (our attempts) to help
resolve the issue using generalized
methods may be helpful or futile. At
least 707 issues are now resolved <grin>.

I hope that when you get issue 708 resolved
you can followup on this thread and let
us know what you discovered.

if by chance you still can't get it
resolved, i don't mind taking addtional
shots at the problem....

- db






OK guys, I've done it all and still get the error message. I also went to
the SQL forum recommended by Rock and posted this message:

I have the exact same problem running Windows XP Pro/SP2, and would like to
fix it. Surly someone here must know how to do it. Here's what I've done so
far w/ no help:

--I ran eusing registry cleaner and "fixed" 707 problems
--I ran msconfig and could find nothing like SQLDUMPER in the Startup lines
to uncheck
--Then I ran sfc /scannow followed by Disk CleanUp w/ no change

A couple other things: 1. The problem started after I uninstalled Microsoft
Accounting 2007, a new program that I do not even know when or why I
downloaded to my computer. It may be purely coincidental, but that is when it
started. I'd go back to a Restore Point, but I don't know when installed the
software. 2. The error message ends w/ this "...Please uninstall then re-run
setup to correct this problem." The problem is I do not know what to
uninstall or what setup to re-run.

PLEASE HELP...

Any other ideas?

 

[db]

1) I enjoy my posting length
and do so without care to your likes or
dislike. Certainly, you are not
in position to supersede current
policies for this newsgroup but clearly
your ego seems to think otherwise.

2) if you are much smarter than
the programmers at Microsoft and
those who designed their registry
cleaner, feel free to provide your
objections to them. i'm sure that
your credentials as MVP will weigh
heavily against their years of directly
programming windows.....


db wrote:

(snip another unreadable post)

I hardly think that a person such as yourself who isn't able to fix his
own posting line length is qualified to provide computer tech support or
an opinion on using registry cleaners.

Malke

 

[Rock]

"db" <databaseben.discussions.microsoft.com> wrote
unfortunately, you know it's one thing
to express a contradiction
based on a lack of experience.

however it is another to contradict
the experts who have been
creating registry cleaners for
their o.s.'s and the hand that
feeds your ego.

You know them as Microsoft
as in Microsoft MVP and
Windows as in the operating
system that you profess to
be experienced with.

the statement you provided
regarding the registry is
inaccurate and directly
contradicts this:

http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm

what's so disturbing is
that your fellow MVP's may
not be providing you with
guidance and education
that can.....

honestly, if you are actually
a Microsoft MVP you should
be providing support for
their software like Microsoft's OneCare

________________

More total drivel on your part. If you had any common sense you would try
to learn something from the regulars who post in here. I will not waste any
more effort on you, but I will continue, as I am sure others will as well,
to post whereever necessary to debunk the garbage you throw out.

--
Rock [MS-MVP User/Shell]

Found it and ran it: It found 707 "problems" and "repaired" them. My
system
seems a little peppier now but I still get the "SQLDUMPER library does not
initialize..." Any idea what it is and how one might go about reinstalling
it? THANKS for trying to help.

I'm glad you aren't seeing any immediate problems from using a registry
cleaner, nor does it surprise me that running it didn't fix your problem
There are two sides to the issue of using one, so let me state my side.

You should not use a registry cleaner. There is generally no advantage to
cleaning the registry, but problems can occur as a result of using one.
Unused entries in the registry do not, in general, cause problems. If
there
is a problem that is associated with an entry in the registry the way to
deal with this is to manually edit the registry. When using an automated
registry cleaner, you're at the whim of the program as it decides what is
not needed; unfortunately the problem is it can remove something that is
needed at some time later, and then suddenly for what appears to be no
apparent reason, a problem surfaces.

Different cleaners will differ in how aggressive they are in making
suggestions on what to remove, but the basic fact is that removing
orphaned
entries doesn't do much. It's a mental placebo.

I suggest if that program has a undo feature you use it. The only way to
use a registry cleaner is for suggestions on what needs to be changed,
which
you should research to see if those changes are needed, and make changes
one
or just a few at a time.

As to your issue, who is the author for Windows Accounting 2007? Is that
the software name? You could contact their tech support for info . Also
you could do some reading in these links:

http://www.google.com/search?hl=en&q=SQLDUMPER+library+does+not+initialize+or+is+corrupt

 

[Rock]

OK guys, I've done it all and still get the error message. I also went to
the SQL forum recommended by Rock and posted this message:

I have the exact same problem running Windows XP Pro/SP2, and would like
to
fix it. Surly someone here must know how to do it. Here's what I've done
so
far w/ no help:

--I ran eusing registry cleaner and "fixed" 707 problems
--I ran msconfig and could find nothing like SQLDUMPER in the Startup
lines
to uncheck
--Then I ran sfc /scannow followed by Disk CleanUp w/ no change

A couple other things: 1. The problem started after I uninstalled
Microsoft
Accounting 2007, a new program that I do not even know when or why I
downloaded to my computer. It may be purely coincidental, but that is when
it
started. I'd go back to a Restore Point, but I don't know when installed
the
software. 2. The error message ends w/ this "...Please uninstall then
re-run
setup to correct this problem." The problem is I do not know what to
uninstall or what setup to re-run.

PLEASE HELP...

Any other ideas?

Gene as I said before using a registry cleaner is highly unlikely to fix
your issue, it generally does nothing to help your system and quite often
causes more problems as a result of it's deletions.

If it has an undo feature use it to undo the changes it made to those 707
entries, and get rid of the program. Try Malke's suggestion of a system
restore. You could also post to this forum which is specific for that
program. I just located it.

http://www.microsoft.com/office/com...dg=microsoft.public.sba.general&lang=en&cr=US

Good luck.

 

[Guest]

Success! ...of a sort. I ran services.msc and disabelled SQL Server VSS
Writer, which "provides the interface to backup/restore Microsoft SQL server
throught the Windowss VSS infrastructure." I don't know what that means, but
wonder what effect/s it will have on which programs and processes down the
road. Any ideas?

OK guys, I've done it all and still get the error message. I also went to
the SQL forum recommended by Rock and posted this message:

I have the exact same problem running Windows XP Pro/SP2, and would like to
fix it. Surly someone here must know how to do it. Here's what I've done so
far w/ no help:

--I ran eusing registry cleaner and "fixed" 707 problems
--I ran msconfig and could find nothing like SQLDUMPER in the Startup lines
to uncheck
--Then I ran sfc /scannow followed by Disk CleanUp w/ no change

A couple other things: 1. The problem started after I uninstalled Microsoft
Accounting 2007, a new program that I do not even know when or why I
downloaded to my computer. It may be purely coincidental, but that is when it
started. I'd go back to a Restore Point, but I don't know when installed the
software. 2. The error message ends w/ this "...Please uninstall then re-run
setup to correct this problem." The problem is I do not know what to
uninstall or what setup to re-run.

Registry cleaners are dangerous in unskilled hands and in any case would
not help with your error. You need to either contact Microsoft
Accounting 2007 tech support - and this could not have magically
installed by itself, you must have installed it with something - perhaps
an MS Office 2007 trial - or do a System Restore.

You will be able to tell which System Restore point to restore to be
looking at them. When you highlight the dates in bold on the System
Restore calendar on the left, look on the right panel. This will say
what happened. If you are fortunate, you'll see an entry made just
before you installed MS Accounting. That's the restore point you want.
If you are unfortunate and can't find such an entry, then surely you
remember roughly when you installed this new program. Pick a date before
that with the understanding that going back more than a few weeks isn't
a good idea.

I also doubt that you would see an entry in msconfig for SQLDUMPER since
this is only produced when there is an error in whatever is using SQL.
You should be looking for something Office-related that is set to start
with Windows.

You might also see if there is a SQL service running and temporarily
disable it. This is only useful and safe if you have no other programs
using SQL. If you are a home user, you probably don't. To do this:

Start>Run>services.msc [enter]

Scroll down until you see the correct SQL entry, double-click it, stop
the service and set it to disabled.

Here is the homepage for Microsoft Office Accounting Professional:
http://office.microsoft.com/en-us/accounting/default.aspx


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

 

[Guest]

Not sure if my last post went through, so I'll repeat:

Success! ...Of sorts. I ran the services.msc utility and Disabled SQL Server
VSS Writer, which "provides the interface to backup/restore Microsoft SQL
server throught the Windowss VSS infrastructure." Whatever that means... The
problem is I don't know what effect/s that will have on other programs and
processes down the road. Any ideas?

OK guys, I've done it all and still get the error message. I also went to
the SQL forum recommended by Rock and posted this message:

I have the exact same problem running Windows XP Pro/SP2, and would like to
fix it. Surly someone here must know how to do it. Here's what I've done so
far w/ no help:

--I ran eusing registry cleaner and "fixed" 707 problems
--I ran msconfig and could find nothing like SQLDUMPER in the Startup lines
to uncheck
--Then I ran sfc /scannow followed by Disk CleanUp w/ no change

A couple other things: 1. The problem started after I uninstalled Microsoft
Accounting 2007, a new program that I do not even know when or why I
downloaded to my computer. It may be purely coincidental, but that is when it
started. I'd go back to a Restore Point, but I don't know when installed the
software. 2. The error message ends w/ this "...Please uninstall then re-run
setup to correct this problem." The problem is I do not know what to
uninstall or what setup to re-run.

Registry cleaners are dangerous in unskilled hands and in any case would
not help with your error. You need to either contact Microsoft
Accounting 2007 tech support - and this could not have magically
installed by itself, you must have installed it with something - perhaps
an MS Office 2007 trial - or do a System Restore.

You will be able to tell which System Restore point to restore to be
looking at them. When you highlight the dates in bold on the System
Restore calendar on the left, look on the right panel. This will say
what happened. If you are fortunate, you'll see an entry made just
before you installed MS Accounting. That's the restore point you want.
If you are unfortunate and can't find such an entry, then surely you
remember roughly when you installed this new program. Pick a date before
that with the understanding that going back more than a few weeks isn't
a good idea.

I also doubt that you would see an entry in msconfig for SQLDUMPER since
this is only produced when there is an error in whatever is using SQL.
You should be looking for something Office-related that is set to start
with Windows.

You might also see if there is a SQL service running and temporarily
disable it. This is only useful and safe if you have no other programs
using SQL. If you are a home user, you probably don't. To do this:

Start>Run>services.msc [enter]

Scroll down until you see the correct SQL entry, double-click it, stop
the service and set it to disabled.

Here is the homepage for Microsoft Office Accounting Professional:
http://office.microsoft.com/en-us/accounting/default.aspx


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

 

[db]

that's good you found it.

services is one part of the
whole picture / o.s....


Not sure if my last post went through, so I'll repeat:

Success! ...Of sorts. I ran the services.msc utility and Disabled SQL Server
VSS Writer, which "provides the interface to backup/restore Microsoft SQL
server throught the Windowss VSS infrastructure." Whatever that means... The
problem is I don't know what effect/s that will have on other programs and
processes down the road. Any ideas?

OK guys, I've done it all and still get the error message. I also went to
the SQL forum recommended by Rock and posted this message:

I have the exact same problem running Windows XP Pro/SP2, and would like to
fix it. Surly someone here must know how to do it. Here's what I've done so
far w/ no help:

--I ran eusing registry cleaner and "fixed" 707 problems
--I ran msconfig and could find nothing like SQLDUMPER in the Startup lines
to uncheck
--Then I ran sfc /scannow followed by Disk CleanUp w/ no change

A couple other things: 1. The problem started after I uninstalled Microsoft
Accounting 2007, a new program that I do not even know when or why I
downloaded to my computer. It may be purely coincidental, but that is when it
started. I'd go back to a Restore Point, but I don't know when installed the
software. 2. The error message ends w/ this "...Please uninstall then re-run
setup to correct this problem." The problem is I do not know what to
uninstall or what setup to re-run.

Registry cleaners are dangerous in unskilled hands and in any case would
not help with your error. You need to either contact Microsoft
Accounting 2007 tech support - and this could not have magically
installed by itself, you must have installed it with something - perhaps
an MS Office 2007 trial - or do a System Restore.

You will be able to tell which System Restore point to restore to be
looking at them. When you highlight the dates in bold on the System
Restore calendar on the left, look on the right panel. This will say
what happened. If you are fortunate, you'll see an entry made just
before you installed MS Accounting. That's the restore point you want.
If you are unfortunate and can't find such an entry, then surely you
remember roughly when you installed this new program. Pick a date before
that with the understanding that going back more than a few weeks isn't
a good idea.

I also doubt that you would see an entry in msconfig for SQLDUMPER since
this is only produced when there is an error in whatever is using SQL.
You should be looking for something Office-related that is set to start
with Windows.

You might also see if there is a SQL service running and temporarily
disable it. This is only useful and safe if you have no other programs
using SQL. If you are a home user, you probably don't. To do this:

Start>Run>services.msc [enter]

Scroll down until you see the correct SQL entry, double-click it, stop
the service and set it to disabled.

Here is the homepage for Microsoft Office Accounting Professional:
http://office.microsoft.com/en-us/accounting/default.aspx


Malke
--
Elephant Boy Computers
www.elephantboycomputers.com
"Don't Panic!"
MS-MVP Windows - Shell/User

 

[db]

you see, that is your
problem : listening to
the b.s. by some of the
regulars who are bored,
misguided and enjoy
manipulation.

just in case the
"regulars" haven't
mentioned it, you should
take care with your
contradictory comments
for microsoft products.

it won't look good when
i post a comment/talkback
about the MVP's who have issues
with Microsoft Products like
OneCare; when next an e-zine
decides to publish a review.

maybe you should start
listening to those non regular
MVP's. They may not say much
but when they do, it is done with
professionalism and integrity.

- db
"db" <databaseben.discussions.microsoft.com> wrote
unfortunately, you know it's one thing
to express a contradiction
based on a lack of experience.

however it is another to contradict
the experts who have been
creating registry cleaners for
their o.s.'s and the hand that
feeds your ego.

You know them as Microsoft
as in Microsoft MVP and
Windows as in the operating
system that you profess to
be experienced with.

the statement you provided
regarding the registry is
inaccurate and directly
contradicts this:

http://onecare.live.com/site/en-US/article/registry_cleaner_why.htm

what's so disturbing is
that your fellow MVP's may
not be providing you with
guidance and education
that can.....

honestly, if you are actually
a Microsoft MVP you should
be providing support for
their software like Microsoft's OneCare

________________

More total drivel on your part. If you had any common sense you would try
to learn something from the regulars who post in here. I will not waste any
more effort on you, but I will continue, as I am sure others will as well,
to post whereever necessary to debunk the garbage you throw out.

--
Rock [MS-MVP User/Shell]

Found it and ran it: It found 707 "problems" and "repaired" them. My
system
seems a little peppier now but I still get the "SQLDUMPER library does not
initialize..." Any idea what it is and how one might go about reinstalling
it? THANKS for trying to help.

I'm glad you aren't seeing any immediate problems from using a registry
cleaner, nor does it surprise me that running it didn't fix your problem
There are two sides to the issue of using one, so let me state my side.

You should not use a registry cleaner. There is generally no advantage to
cleaning the registry, but problems can occur as a result of using one.
Unused entries in the registry do not, in general, cause problems. If
there
is a problem that is associated with an entry in the registry the way to
deal with this is to manually edit the registry. When using an automated
registry cleaner, you're at the whim of the program as it decides what is
not needed; unfortunately the problem is it can remove something that is
needed at some time later, and then suddenly for what appears to be no
apparent reason, a problem surfaces.

Different cleaners will differ in how aggressive they are in making
suggestions on what to remove, but the basic fact is that removing
orphaned
entries doesn't do much. It's a mental placebo.

I suggest if that program has a undo feature you use it. The only way to
use a registry cleaner is for suggestions on what needs to be changed,
which
you should research to see if those changes are needed, and make changes
one
or just a few at a time.

As to your issue, who is the author for Windows Accounting 2007? Is that
the software name? You could contact their tech support for info . Also
you could do some reading in these links:

http://www.google.com/search?hl=en&q=SQLDUMPER+library+does+not+initialize+or+is+corrupt