Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
DiscussionsAccessExcelInfoPathOutlookPowerPointPublisherWord
DirectoryUser Groups
Related Topics
Outlook ExpressInternet ExplorerWindowsMS Server ProductsMore Topics ...

MS Office Forum / Outlook / Business Contact Manager / May 2007

Tip: Looking for answers? Try searching our database.

SQLDUMPER library failed initialization

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Workmad - 28 May 2007 20:20 GMT
I just recieved a new computer with Office 2007 on it.  After setting up
Outlook the "setup for Business Contact Manager" kept coming up.  Though the
help button on that wizard I finally figured out to get rid of the wizard.  
It told me I must uninstall it.  It took me to an uninstall wizard and asked
if I wanted to uninstall BCM and SQL Server.  I said yes and ever since I am
getting the error:

"SQLDUMPER library failed initialization.  Your installation is either
corrupt or has been tampered with.  Please uninstall then re-run setup to
correct this problem."

In addition, after I ran this uninstall my computer will boot up normal
speed but once my desktop picture loads it sort of stops.  I can not hear the
harddrive clicking and the icons nor the taskbar appear.  It sits there for
maybe 3-4 minutes (an eternity) then the harddrive starts clicking again, the
icons appear and it finishes loading.
Luther - 29 May 2007 16:21 GMT
On May 28, 12:20 pm, Workmad <Work...@discussions.microsoft.com>
wrote:
> I just recieved a new computer with Office 2007 on it.  After setting up
> Outlook the "setup for Business Contact Manager" kept coming up.  Though the
[quoted text clipped - 12 lines]
> maybe 3-4 minutes (an eternity) then the harddrive starts clicking again, the
> icons appear and it finishes loading.  

Sounds like some application or utility expects to find Sql Server,
and now hangs until its attempts to access sql timeout.

You could start by looking in the event logs for errors during start
up.

It is also possible that the sql uninstall did not complete
successfully and left behind some service that's trying to connect to
sql server, although this is less likely to tie up your desktop.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.