| Author |
Message |
smcleod
Joined: 24 Nov 2009
Posts: 3
|
 Posted: Tue Aug 21, 2012 2:40 pm Post subject: SQL 2012 - Compatible?? |
 |
|
| 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! |
|
| Back to top |
|
 |
colinbo
Joined: 15 Feb 2006
Posts: 10
|
| Posted: Fri Aug 24, 2012 9:22 pm Post subject: |
|
|
I hit the same issue packaging any database residing on a SQL 2012 instance. I turned on verbose logging but it doesn't give much in the way of hints:
| Code: |
16:20:19.495|Info |Logging |1 |Current Logging levels enabled: Verbose,Warning,Fatal,Debug,Information,Trace,Error
16:20:28.292|Info |SQL Compare Engine |6 |Register live database start: FOO
16:20:28.292|Info |SQL Compare Engine |6 |Populate Live Start, popoptions: #rJg, #wJg
16:20:28.292|Info |SQL Compare Engine |6 |Populate Live Start, options: DoNotOutputCommentHeader, IgnoreUsers, Default
16:20:28.308|Info |SQL Compare Engine |6 |Populate major version: SqlServer2008
16:20:28.308|Info |SQL Compare Engine |6 |Populate got casing: False
16:20:28.308|Info |SQL Compare Engine |6 |Populate Case Sensitive: False
16:20:28.323|Info |SQL Compare Engine |6 |Populate FulltextCatalogs start.
16:20:28.323|Info |SQL Compare Engine |6 |Populate Fulltext Stoplists start.
16:20:28.323|Info |SQL Compare Engine |6 |Populate Fulltext Stopwords start.
16:20:28.323|Info |SQL Compare Engine |6 |Populate ObjectNames start.
|
|
|
| Back to top |
|
|
carltierney
Joined: 17 Sep 2012
Posts: 2
Location: Dallas TX
|
| Posted: Thu Sep 20, 2012 4:23 am Post subject: Same issue... can't package because of the ExecuteReader |
|
|
http://imgur.com/UzECV
Here is what I see from trying to use the packager with 2012. |
|
| Back to top |
|
|
Brian Donahue
Joined: 23 Aug 2004
Posts: 6344
Location: Red Gate Software
|
|
| Back to top |
|
|
colbybhearn
Joined: 27 Sep 2012
Posts: 5
|
| Posted: Thu Oct 11, 2012 4:48 pm Post subject: Re: |
|
|
I just upgraded to SQL 2012 and was getting the same message. "ExecuteReader: CommandText property has not been initialized"
Thanks Brian, that small patch immediately fixed it.
-Colby |
|
| Back to top |
|
|
rbelbin
Joined: 12 Oct 2012
Posts: 1
|
| Posted: Fri Oct 12, 2012 5:53 pm Post subject: Re: |
|
|
I tried this package, and after it installed it basically removed the trial period from all of the SQL developer Toolbelt products. Any work around to that? |
|
| Back to top |
|
|
colbybhearn
Joined: 27 Sep 2012
Posts: 5
|
| Posted: Fri Oct 12, 2012 11:11 pm Post subject: Command Line Functionality |
|
|
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.
Here is the command line input/output: (carefully redacted)
| Code: |
C:\Users\MyUsername>"C:\Program Files (x86)\Red Gate\SQL Packager 6\sqlpackager.exe" /verbose /server1:BuildServer /database1:"Ref_Database" /includedata:Table /rundatabase:"Db_Install_Name" /exe /name:"Db_Installer_Filename" /location:"C:\Program Files (x86)\RedGateOutpus\Installers" > C:\Users\MyUsername\Desktop\sql5.txt
Error: Object reference not set to an instance of an object. |
Here is the content of the sql5.txt file:
| Code: |
SQL Packager Command Line V6.6.0.347
==============================================================================
Copyright c Red Gate Software Ltd 1999-2008
SQL Compare running with option: IgnoreFillFactor (OK).
SQL Compare running with option: IgnoreWhiteSpace (OK).
SQL Compare running with option: IncludeDependencies (OK).
SQL Compare running with option: IgnoreFileGroups (OK).
SQL Compare running with option: IgnoreUserProperties (OK).
SQL Compare running with option: IgnoreWithElementOrder (OK).
SQL Compare running with option: DecryptPost2kEncryptedObjects (OK).
Comparing database BuildServer.Ref_Database with database ....
Registering data sources
Creating mappings
Comparing
Applying Command Line Items
Retrieving migration scripts
Creating SQL
Summary Information
===============================================================================
DB1 = BuildServer.Ref_Database
DB2 =
Object type Name DB1 DB2
-------------------------------------------------------------------------------
...Proper Object Enumeration Here...
-------------------------------------------------------------------------------
Details - comparing BuildServer.Ref_Database with
===============================================================================
...Proper Object Content Here...
-------------------------------------------------------------------------------
Used mapping option 'IgnoreSpaces'
Used mapping option 'IncludeTimestamps'
Used mapping option 'IncludeIdentities'
Used Sql Option 'DisableKeys'
Used Sql Option 'DontOutputComments'
SQL Data Compare running with Mapping Option: IgnoreSpaces (OK).
SQL Data Compare running with Mapping Option: IncludeTimestamps (OK).
SQL Data Compare running with Mapping Option: IncludeIdentities (OK).
SQL Data Compare running with SQL Option: DisableKeys (OK).
SQL Data Compare running with SQL Option: DontOutputComments (OK).
SQL Data Compare running with Mapping Option: MissingFrom2AsInclude (OK).
Comparing database BuildServer.Ref_Database with database ....
Registering databases
Mapping
|
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 |
|
| Back to top |
|
|
Brian Donahue
Joined: 23 Aug 2004
Posts: 6344
Location: Red Gate Software
|
| Posted: Mon Oct 15, 2012 9:32 am Post subject: |
|
|
Hi,
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.
_________________
Brian Donahue
Technical Support
Red Gate Software Ltd.
44 (0)870 160 0037 ext 8521
US and CAN 1-866-RED GATE ext 8521 |
|
| Back to top |
|
|
colbybhearn
Joined: 27 Sep 2012
Posts: 5
|
| Posted: Mon Oct 15, 2012 2:43 pm Post subject: SQL 2012 Compatibility |
|
|
Hey Brian,
I totally understand. Thanks for relaying the concerns.
-Colby |
|
| Back to top |
|
|
Calvin
Joined: 14 Jan 2013
Posts: 1
|
| Posted: Mon Jan 14, 2013 2:10 pm Post subject: |
|
|
| Any news on this being completed? I use Packager quite a bit and am getting close to my license renewal. |
|
| Back to top |
|
|
dw5304
Joined: 02 Apr 2013
Posts: 1
|
| Posted: Tue Apr 02, 2013 8:54 pm Post subject: |
|
|
| having same issue as listed above with patch 6.6.0.347 any eta on fix? |
|
| Back to top |
|
|
|
