IT Answers » SQL writer

SQL Server 2005 Express SP3 Memory Usage

Ndea447 — Thu, 06 May 2010 12:50:00 +0000

Upon Startup of my system the sqlwriter process immediately grabs 700mb of RAM and holds it. As I use the SQL Server to do different thing the memory usage grows and causes the memory on my system to decline. The SQL Server never releases the memory and it causes my system to respond slowly. I fear that if left unchecked it might cause the system to freeze.

SQL Writer library failed initialization

Valeverger — Thu, 02 Apr 2009 01:37:11 +0000

SQL Writer library failed initialization. Your installattion iseither corrupt or has been tampered with.
Please uninstall then re-run setupto correct this problem.
How should I handle this?

SQL Writer error

Chuanilee — Fri, 16 Jan 2009 00:58:35 +0000

sql error in the start; either mesup or tempered

SQL Writer error message – SQLDUMPER library failed

Mmichals1 — Sun, 21 Dec 2008 18:09:29 +0000

error sql writer – sql dumper liabrary failed initialization install corrupt or tamper with

SQL Writer

Wnic — Sat, 29 Nov 2008 13:39:09 +0000

SQL Writer library failed initialization. Your installattion iseither corrupt or has been tampered with.
Please uninstall then re-run setupto correct this problem.
How should I handle this?

Microsoft Sequel Server 2005 VSS backup

LeonT — Thu, 13 Nov 2008 11:45:00 +0000

What’s seems to have happened is that the SQLVDI.dll files in the 2 directories:
C:\Program Files (x86)\Microsoft SQL Server\80\COM C:\Program Files\Microsoft SQL Server\80\COM

are out of sync. This seems to have happened as a result of a service pack for MSSQL which was applied in Dev.
The Microsoft Sequel VSS writer is unable to initialize correctly and as a result of this interface not functioning properly, SQL Backup is unable to initialize.

In order to get the versions of the SQLVDI.dll in sync again I copied the latest SQLVDI.dll from another server unregistered the out of sync version and reregistered the matching version. The SQL Backup service failed to start.
This problem is on Microsoft Sequel 2005 SP2 running on Windows Server 2008 on Windows Hyper V platform. Microsoft released an untested patch for this problem, however, it says that the patch is not applicable when I attempt to run it on the system. I then put everything back as it was (out of sync) and the service runs but cannot backup or restore.

By completely uninstalling Microsoft Sequel server including workstation components, VSS writer, Database Engine, Integration services and Full Text search engine, Red Gate Backup and then deleting all folders relevant to these installations, rebooting and reinstalling everything again, solves the problem. An uninstall of just the Database engine and Red Gate Backup does not solve the problem.

Anyway, uninstalling everything isn’t a solution. Have uninstalled and reintsalled VSS writer by itself.

I’ve tried everything and nothing. Even tried to switch the reg key enabling VSS SQL Writer in an attempt to get it to use MSDE writer instead and no go. I’ll try anything at this point…