I just spent 4 hours of frustration, trying to debug a problem with SQL
2000. It was self-inflicted, as it turned out, but I could have fixed
the problem in 5 minutes instead of 4 hours if the @.#%@.#$% error
message:
"String or binary data would be truncated"
would give some CLUES! How about a field name, or even the data that
it's trying to put into the mystery field in some mystery table? And
why not tell me whether it's actually a string or binary data, not
lumping them both together. (I envision a mythical error message that
says "You have caused a numeric overflow, or underflow, or divide by
zero, or there's a key violation, or a trigger is not defined, or the
statement syntax is wrong." Which might be a perfectly correct but not-
helpful error message.)
I was convinced that I was trying to put a single character 'C' into a
field defined as Char(2), and I was tearing my hair out. Aaargh.
The actual Update statement was buried in the guts of a DTS transform,
but this isn't a DTS complaint, it's a SQL error message complaint.
When you try to put a null into a field that can't accept nulls, at
least the error message gives you the name of the field that you're
trying to update. That is infinitely more helpful than this stupid
truncation message. (And I don't want to turn warnings off; in this
case, I was trying to put the wrong value into a different field, so the
error was important -- but I wasn't being pointed to the right place.)
A little help from the error message would be nice.
Hmmm. I wonder if the new upcoming SQL does a better job. I'll have to
ask someone over there.
David WalkerYOu sure have to give us some mistery SQL Query or magic DDL to understand
whats going on, seems that one column is truncated.
HTH, Jens Suessmeyer.
--
http://www.sqlserver2005.de
--
"DWalker" <none@.none.com> schrieb im Newsbeitrag
news:OUBF6SnSFHA.3356@.TK2MSFTNGP12.phx.gbl...
>I just spent 4 hours of frustration, trying to debug a problem with SQL
> 2000. It was self-inflicted, as it turned out, but I could have fixed
> the problem in 5 minutes instead of 4 hours if the @.#%@.#$% error
> message:
> "String or binary data would be truncated"
> would give some CLUES! How about a field name, or even the data that
> it's trying to put into the mystery field in some mystery table? And
> why not tell me whether it's actually a string or binary data, not
> lumping them both together. (I envision a mythical error message that
> says "You have caused a numeric overflow, or underflow, or divide by
> zero, or there's a key violation, or a trigger is not defined, or the
> statement syntax is wrong." Which might be a perfectly correct but not-
> helpful error message.)
> I was convinced that I was trying to put a single character 'C' into a
> field defined as Char(2), and I was tearing my hair out. Aaargh.
> The actual Update statement was buried in the guts of a DTS transform,
> but this isn't a DTS complaint, it's a SQL error message complaint.
> When you try to put a null into a field that can't accept nulls, at
> least the error message gives you the name of the field that you're
> trying to update. That is infinitely more helpful than this stupid
> truncation message. (And I don't want to turn warnings off; in this
> case, I was trying to put the wrong value into a different field, so the
> error was important -- but I wasn't being pointed to the right place.)
> A little help from the error message would be nice.
> Hmmm. I wonder if the new upcoming SQL does a better job. I'll have to
> ask someone over there.
>
> David Walker|||David,
I agree that error less-informative messages as a pain to work with. Did you consider posting to
sqlwish@.microsoft.com on this case?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/|||I figured out my problem, the complaint is that the error message is not
very helpful. I was not looking for more assistance, I was just
complaining about the error message... But thanks!
David
"Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
in news:#QWpPWnSFHA.1312@.TK2MSFTNGP14.phx.gbl:
> YOu sure have to give us some mistery SQL Query or magic DDL to
> understand whats going on, seems that one column is truncated.
> HTH, Jens Suessmeyer.
> --
> http://www.sqlserver2005.de
> --
> "DWalker" <none@.none.com> schrieb im Newsbeitrag
> news:OUBF6SnSFHA.3356@.TK2MSFTNGP12.phx.gbl...
>>I just spent 4 hours of frustration, trying to debug a problem with
>>SQL
>> 2000. It was self-inflicted, as it turned out, but I could have
>> fixed the problem in 5 minutes instead of 4 hours if the @.#%@.#$%
>> error message:
>> "String or binary data would be truncated"
>> would give some CLUES! How about a field name, or even the data that
>> it's trying to put into the mystery field in some mystery table? And
>> why not tell me whether it's actually a string or binary data, not
>> lumping them both together. (I envision a mythical error message
>> that says "You have caused a numeric overflow, or underflow, or
>> divide by zero, or there's a key violation, or a trigger is not
>> defined, or the statement syntax is wrong." Which might be a
>> perfectly correct but not- helpful error message.)
>> I was convinced that I was trying to put a single character 'C' into
>> a field defined as Char(2), and I was tearing my hair out. Aaargh.
>> The actual Update statement was buried in the guts of a DTS
>> transform, but this isn't a DTS complaint, it's a SQL error message
>> complaint.
>> When you try to put a null into a field that can't accept nulls, at
>> least the error message gives you the name of the field that you're
>> trying to update. That is infinitely more helpful than this stupid
>> truncation message. (And I don't want to turn warnings off; in this
>> case, I was trying to put the wrong value into a different field, so
>> the error was important -- but I wasn't being pointed to the right
>> place.)
>> A little help from the error message would be nice.
>> Hmmm. I wonder if the new upcoming SQL does a better job. I'll have
>> to ask someone over there.
>>
>> David Walker
>|||"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
in news:uzUDsVnSFHA.3712@.TK2MSFTNGP10.phx.gbl:
> David,
> I agree that error less-informative messages as a pain to work with.
> Did you consider posting to sqlwish@.microsoft.com on this case?
>
I will do that, thanks.
David|||ok. Gotit. :-)
"DWalker" <none@.none.com> schrieb im Newsbeitrag
news:O763lynSFHA.3176@.TK2MSFTNGP09.phx.gbl...
>I figured out my problem, the complaint is that the error message is not
> very helpful. I was not looking for more assistance, I was just
> complaining about the error message... But thanks!
> David
>
> "Jens Süßmeyer" <Jens@.Remove_this_For_Contacting.sqlserver2005.de> wrote
> in news:#QWpPWnSFHA.1312@.TK2MSFTNGP14.phx.gbl:
>> YOu sure have to give us some mistery SQL Query or magic DDL to
>> understand whats going on, seems that one column is truncated.
>> HTH, Jens Suessmeyer.
>> --
>> http://www.sqlserver2005.de
>> --
>> "DWalker" <none@.none.com> schrieb im Newsbeitrag
>> news:OUBF6SnSFHA.3356@.TK2MSFTNGP12.phx.gbl...
>>I just spent 4 hours of frustration, trying to debug a problem with
>>SQL
>> 2000. It was self-inflicted, as it turned out, but I could have
>> fixed the problem in 5 minutes instead of 4 hours if the @.#%@.#$%
>> error message:
>> "String or binary data would be truncated"
>> would give some CLUES! How about a field name, or even the data that
>> it's trying to put into the mystery field in some mystery table? And
>> why not tell me whether it's actually a string or binary data, not
>> lumping them both together. (I envision a mythical error message
>> that says "You have caused a numeric overflow, or underflow, or
>> divide by zero, or there's a key violation, or a trigger is not
>> defined, or the statement syntax is wrong." Which might be a
>> perfectly correct but not- helpful error message.)
>> I was convinced that I was trying to put a single character 'C' into
>> a field defined as Char(2), and I was tearing my hair out. Aaargh.
>> The actual Update statement was buried in the guts of a DTS
>> transform, but this isn't a DTS complaint, it's a SQL error message
>> complaint.
>> When you try to put a null into a field that can't accept nulls, at
>> least the error message gives you the name of the field that you're
>> trying to update. That is infinitely more helpful than this stupid
>> truncation message. (And I don't want to turn warnings off; in this
>> case, I was trying to put the wrong value into a different field, so
>> the error was important -- but I wasn't being pointed to the right
>> place.)
>> A little help from the error message would be nice.
>> Hmmm. I wonder if the new upcoming SQL does a better job. I'll have
>> to ask someone over there.
>>
>> David Walker
>>
>
Showing posts with label fixed. Show all posts
Showing posts with label fixed. Show all posts
Sunday, March 11, 2012
Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005
Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?
05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181
Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?
Thanks,
Samuel Lester (MSFT)
From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
Please reboot and try again. May be SNAC reboot has halted the installation until reboot.
|||did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error
'failed because a higher version already exists on the machine'
Is it safe to uninstall backward compatability and reinstall it?
Thanks,
Kerry
|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005
Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?
05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181
Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?
Thanks,
Samuel Lester (MSFT)
From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
Please reboot and try again. May be SNAC reboot has halted the installation until reboot.
|||did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error
'failed because a higher version already exists on the machine'
Is it safe to uninstall backward compatability and reinstall it?
Thanks,
Kerry
|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.Backward Compatibility Upgrade failed on Service Pack 1 for SQL Server 2005
Not sure if this gets fixed on a restart, but the Backward Compatibility upgrade/piece failed on service pack 1 install for SQL Server 2005. Here is the log output. Anyone experience this?
05/19/2006 08:58:27.648 ================================================================================
05/19/2006 08:58:27.648 Hotfix package launched
05/19/2006 09:00:04.368 Attempting to install instance: SQL Server Native Client
05/19/2006 09:00:04.383 Attempting to install target: CLARITY
05/19/2006 09:00:04.383 Attempting to install file: sqlncli.msi
05/19/2006 09:00:04.399 Attempting to install file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:04.399 Creating MSI install log file at: C:\WINDOWS\Hotfix\Redist9\Logs\Redist9_Hotfix_KB913090_sqlncli.msi.log
05/19/2006 09:00:04.415 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:04.415 Failed to read registry key: Debug
05/19/2006 09:00:51.040 MSP returned 3010: A restart is required to complete the install. This message is indicative of a success. This does not include installs where the ForceReboot action is run. This error code is not available on Windows Installer version 1.0.
05/19/2006 09:00:51.118 Successfully opened registry key: Software\Policies\Microsoft\Windows\Installer
05/19/2006 09:00:51.118 Failed to read registry key: Debug
05/19/2006 09:00:51.118 Pending reboot, successfully installed file: \\<server>\s$\917f50731dade382ab1b\HotFixSqlncli\Files\sqlncli.msi
05/19/2006 09:00:51.134 Successfully installed target: <SERVER>
05/19/2006 09:00:51.134 Successfully installed instance: SQL Server Native Client
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product Status Summary:
05/19/2006 09:00:51.134 Product: SQL Server Native Client
05/19/2006 09:00:51.134 SQL Server Native Client (RTM ) - Reboot Required
05/19/2006 09:00:51.134
05/19/2006 09:00:51.134 Product: Setup Support Files
05/19/2006 09:00:51.134 Setup Support Files (RTM ) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Database Services
05/19/2006 09:00:51.150 Database Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150 Reporting Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Notification Services
05/19/2006 09:00:51.150 Notification Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Integration Services
05/19/2006 09:00:51.150 Integration Services (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.150
05/19/2006 09:00:51.150 Product: Client Components
05/19/2006 09:00:51.165 Client Components (RTM 1399 ENU) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: MSXML 6.0 Parser
05/19/2006 09:00:51.165 MSXML 6.0 Parser (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: SQLXML4
05/19/2006 09:00:51.165 SQLXML4 (RTM ) - Not Applied
05/19/2006 09:00:51.165
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
05/19/2006 09:00:51.181
05/19/2006 09:00:51.181 Product: Microsoft SQL Server VSS Writer
05/19/2006 09:00:51.181 Microsoft SQL Server VSS Writer (RTM ) - Not Applied
05/19/2006 09:00:51.181
Are there any other logs created other than this one? If so, can you search for the "return value 3" in them and send the +/- 10 lines on each side of that error for us to debug?
Thanks,
Samuel Lester (MSFT)
From your log info, it does not look like Hotfix even attempted to install on Backward Compatibility redist.
05/19/2006 09:00:51.165 Product: Backward Compatibility
05/19/2006 09:00:51.165 Backward Compatibility (RTM ) - Not Applied
Please reboot and try again. May be SNAC reboot has halted the installation until reboot.
|||did you find a solution for this? I have the same problem. I am running a named instance of sql server 2005 standard edition and a default instance of sql server 2000 enterprise. I removed the default instance to install a new version of sql server 2005 as default, but I am unable to install it because of the backward compatability. I have managed to put 2000 back on as the default instance. Now i cannot apply service pack 1 to my named instance and i cannot install analysis server. I have tried to run sqlserver2005_bc.msi but get the error
'failed because a higher version already exists on the machine'
Is it safe to uninstall backward compatability and reinstall it?
Thanks,
Kerry
|||This has been so long ago, I don't remember what came out of this. Sorry for not catching your response sooner.
Subscribe to:
Posts (Atom)