This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: InstallShield 2010 SQL Script multi line comment bug?
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 14, 2011
06:27 AM
InstallShield 2010 SQL Script multi line comment bug?
I think I found a bug with multi-line comments and SQL scripts in InstallShield 2010.
To reproduce the bug, create a basic MSI project. Go to Installation Designer -> SQL Scripts, create a SQL connection then add a new script that contains the following script:
/*
USE [master]
GO
*/
USE master
GO
Build the MSI and try to install it, you will receive the following MSI error:
Error 27506.Error executing SQL script sqlscript.sql. Line 3. Missing end comment mark '*/'. (113)
Changing the multi-line comment to -- form will solve the issue. Also, if the end comment mark is not being preceded by a GO statement, the install will not fail. For instance:
/*
THIS
WILL
NOT
FAIL
*/
Has someone experienced this bug? Any way to "fix" it?
To reproduce the bug, create a basic MSI project. Go to Installation Designer -> SQL Scripts, create a SQL connection then add a new script that contains the following script:
/*
USE [master]
GO
*/
USE master
GO
Build the MSI and try to install it, you will receive the following MSI error:
Error 27506.Error executing SQL script sqlscript.sql. Line 3. Missing end comment mark '*/'. (113)
Changing the multi-line comment to -- form will solve the issue. Also, if the end comment mark is not being preceded by a GO statement, the install will not fail. For instance:
/*
THIS
WILL
NOT
FAIL
*/
Has someone experienced this bug? Any way to "fix" it?
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jul 14, 2011
10:08 AM
I don't think I've seen this yet, but we did run into length limitation issues with Installshield with the identical error, and their support had confirmed it was too large for IS to handle. Our DBA had commented out a large block as they were testing a new section. The giant blocked caused an overrun (worked fine in SQL Mgmnt Studio.)
-Mike
-Mike