SQLDUMPER library error message (PLEASE HELP)

[Tom Willett]

You need to also get some help for your problem.

"db" <databaseben.discussions.microsoft.com> wrote in message
you see, that is your
problem : listening to
the b.s. by some of the
regulars who are bored,
misguided and enjoy
manipulation.

 

[db]

if you are an mvp then
they are your problems.

teach your fledgings
repect and professionalism.

otherwise, they can embarrass
the mvp program and people
enjoy reading the issues regarding
microsoft .

Sounds like interesting headlines:

"Microsoft MVP's who bash Microsoft's OneCare"



You need to also get some help for your problem.

"db" <databaseben.discussions.microsoft.com> wrote in message
you see, that is your
problem : listening to
the b.s. by some of the
regulars who are bored,
misguided and enjoy
manipulation.

 

[db]

forgot to add:

"please"


"db" <databaseben.discussions.microsoft.com> wrote in message if you are an mvp then
they are your problems.

teach your fledgings
repect and professionalism.

otherwise, they can embarrass
the mvp program and people
enjoy reading the issues regarding
microsoft .

Sounds like interesting headlines:

"Microsoft MVP's who bash Microsoft's OneCare"



You need to also get some help for your problem.

"db" <databaseben.discussions.microsoft.com> wrote in message
you see, that is your
problem : listening to
the b.s. by some of the
regulars who are bored,
misguided and enjoy
manipulation.

 

[Rock]

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

I have no first hand experience with this service, but it's not a standard
service in XP, Vista or MS Office. It's possible it was installed with
that accounting software. Here is a link to a Google search about that
service.

http://www.google.com/search?hl=en&q=sql+server+vss+writer

Have you got a response from the forum you posted to and did you post to
that other forum for Windows Accounting Software?

I can't say what other programs disabling this service will affect.
Obviously monitor it and see what happens, but unless you installed some
other particular software that needs it, things should be fine. At some
point, if it's not needed, you'll want to uninstall that service. Some of
those links in that Google search or input from those two forums might help
you.

 

[Rock]

"db" <databaseben.discussions.microsoft.com> wrote
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

--------------------------

You are delusional. The only one talking about MS products or OneCare is
you, just another sad example of your ramblings and drivel.

I am through responding to you in this thread. Keep at it if you want.

--
Rock [MS-MVP User/Shell]


"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

 

[db]

your response herein
is insightful and professional
appearing to be provided without
prejudice or condemnation.

could it be from someone who
is acting like a professional or
is a professional?

we will just have to wait
and see....

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

I have no first hand experience with this service, but it's not a standard
service in XP, Vista or MS Office. It's possible it was installed with
that accounting software. Here is a link to a Google search about that
service.

http://www.google.com/search?hl=en&q=sql+server+vss+writer

Have you got a response from the forum you posted to and did you post to
that other forum for Windows Accounting Software?

I can't say what other programs disabling this service will affect.
Obviously monitor it and see what happens, but unless you installed some
other particular software that needs it, things should be fine. At some
point, if it's not needed, you'll want to uninstall that service. Some of
those links in that Google search or input from those two forums might help
you.