I am trying to package a database running in SQL Server 2012, and I get the error "ExecuteReader: CommandText property has not been initialized"... what could the problem be, or is SQL Packager not compatible with SQL Server 2012?? Thanks in advance!

I hate to pile on another issue, but I think that patch (6.6.0.347) which fixed packaging through the GUI may have broken something else - Packager's command line interface (CLI) functionality seems to have changed. To make sure it was the patch, I re-installed Packager 6.4 and ran my CLI automation to verify it worked again. I then re-patched to 6.6 and changed nothing about the CLI or automation. I ran the CLI automation again and verified it no longer worked.

I have not yet compared product documentation to see if there is some switch that changed or got deprecated.

For clarity, the \"BuildServer\" is SQL Server 2008.
I can't find anything in the event log from Packager.
Is there anything that the patch changed about the CLI?
Is there anything I can do to find out more about what might be going wrong?
I'd greatly appreciate some help.
-Colby

The patch was designed specifically to solve the problem at the top of this thread. Given all of these problems, I would uninstall the patch. I have notified the product manager that there is this problem and that some effort needs to be put into proper support for SQL Server 2012.

I am having the same issue as reported above. I can start SQL Packager (latest version). It can see my server, and the list of databases shows OK. After selecting a database to package, it goes to the next step, but that errors out.

It aborts when in the Register Database step, Reading Assemblies.

It says "ExecuteReader: CommandText property has not been initialized."

And it refuses to do anything else.

Note: I seem to be having similar issues when using SQL Compare too.

I have purchased licenses for both of these for myself, but they seem to be having problems running with SQL Server 2012.

I will try the patch, but it should be noted that your latest and greatest software products seem to be having some "issues" working properly with up-to-date versions of SQL Server.

1) I had to spend time searching for this fix, after your software refused to work in an up-to-date environment.

2) The readme file for that patch is very explicit. It says, "This patch is for the error "must declare scalar variable @pv" when running a package.
DO NOT install this patch unless you have the problem described."

But this was NOT the error I saw, so just installing the patch was an exercise in faith and ignoring your explicit warning.

Again...this was a waste of my time, that should NOT have been necessary.

I'm glad there is a patch, but why hasn't this been incorporated into the main branch? It's been over a year that you have been aware of the problem.

For the record, I really like your products, and use them on a near-daily basis (and I promote your products to my professional colleagues).