Generating SQL script fails

hrosen50hrosen50 Posts: 2
edited November 10, 2009 8:46AM in SQL Packager Previous Versions
With the message: Value cannot be Null. Parameter name: format

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

Thanks,
Hal
· Share on Twitter

Comments

  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    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.
    · Share on Twitter
  • Brian DonahueBrian Donahue Posts: 6,590 Bronze 1
    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.
    · Share on Twitter
Sign In or Register to comment.