when I restart the computer always come a massage telling me that the SQLDUMPER library failed initialization. Your installation is either corrupt or has been tampered with. Please uninstall then re-run setup to correct this problem.
View 2 RepliesWe want to implement a cold DRP strategy here, Is there any info where:
1. To transfer syslogins to DR Server (is BCP in/out sufficient).
2. SQL to extract DTS/Agent jobs from msdb.
3. I am aware of how to fix broken logins.
thanks all,
Paul
Hi,
I have a package which reads data from set of tables, goes thru a script component for some data changes and written to a flat file. To speed up the process, I have created 6 threads of this same sequence, but instead of writting to different files, I am joining the outputs of all 6 scripts components using 'UNION ALL' and writting it to a single file. I have to execute this for different input years and so calling this data flow within a 'Foreach loop' container for multiple years. When I ran this package for single year, it ran without any error. But when I ran it for multiple years (in debug mode), after processing 3 years, the package just stopped running. It does not abort, but just created a SQLDUMPER Error log file with the following contents.
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 2184
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0100C5D0
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
07/08/06 22:59:03, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
07/08/06 22:59:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
07/08/06 22:59:09, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:Program Files (x86)Microsoft SQL Server90SharedErrorDumpsSQLDmpr0002.mdmp
07/08/06 22:59:09, ACTION, DtsDebugHost.exe, Watson Invoke: No
I have searched this forum and saw one thread with this error message, but there is no response for that. Do you guys know what could be the problem?
Thanks.
Does anyone know if this SQL is part of MS Office or is it XP... I haven't figured that out. It says reinstall the program but doesn't say what program. I know I never intentionally installed an SQL program.
At this time I get the same message as everyone seems to be getting - SQL Dumper Library failed... reinstall ....
The problem for me started when I added Office 2007 and added the business contacts program.
Any ideas are appreciated!
I just added a post but I don't see it so here I go agian, sorry if it shows up later and there ends up being two of them.
I started getting the error message - SQL Dumper Library failed ... Please reinstall... it doesn't say what to reinstal. Does anyone know if this is part of Office or XP? My problem started when I added Office 2007 and the additional Business contacts program from the web site.
I did get SQL 2005 and installed it but it says it isn't working. When I click to repair it, it wants the disk, again I don't know what disk or program it wants, although it will not fix it from the XP disk.
Any help would be appreciated!
Hi
I am constantly getting this error message in the Application log after installing SQL 2005 last night followed by SP1 (say 5 times a minutes). See below:
EventType sql90exception, P1 reportingservicesservice.exe, P2 9.0.2047.0, P3 443f5953, P4 sqldumper_unknown_module.dll, P5 0.0.0.0, P6 00000000, P7 0, P8 00e8ed9d, P9 00000000, P10 NIL.
I have reservice packed SQL 2005 but made no difference - it is running on a Windows 2003 server with all the latest MS patches.
Does anyone know the solution or possible solution to this issue?
Thanks
Matt