Generating SQL script fails

Packages and compresses schema and contents of SQL Server databases

Moderators: JonathanWatts, Chris Auckland, David Atkinson, david connell, Anu Deshpande, Michelle Taylor, james.billings, Marianne

Generating SQL script fails

Postby hrosen50 » Mon Nov 02, 2009 10:24 pm

With the message: Value cannot be Null. Parameter name: format

We've been using the Packager without problems until now. Any suggestions?

Thanks,
Hal
hrosen50
 
Posts: 1
Joined: Mon Nov 02, 2009 10:20 pm

Postby Brian Donahue » Wed Nov 04, 2009 3:12 pm

Hi Hal,

I've seen this error a few times lately, but we haven't got a one-shot-wonder for fixing it because it's a data-driven error. Basically there is a LOB like a text or image field and the data can't be retrieved for it.

The background is that this is a generic error thrown by the Microsoft .NET SqlDataReader when it is reading a row of data and trying to cast it as a .NET datatype.

If you can work out which table this is happening on, maybe it would be a good idea to run DBCC CHECKTABLE on it and see if there are any errors.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am

Postby Brian Donahue » Tue Nov 10, 2009 2:46 pm

Hi Hal,

Just to clarify, the suggested cause of the fault that I had proposed deals strictly with this error happening during the generation of a SQL script. If this happens when you're actually executing a SQL Packager Package, the same error message is shown when trying to get the default data and log locations and adding the user running the package to the dbcreator server role will fix it.
Brian Donahue
 
Posts: 6670
Joined: Mon Aug 23, 2004 10:48 am


Return to SQL Packager 6

Who is online

Users browsing this forum: No registered users and 0 guests