HM10044: Error while executing SQL Statement

Use this forum if you have installed hMailServer and want to ask a question related to a production release of hMailServer. Before posting, please read the troubleshooting guide. A large part of all reported issues are already described in detail here.
Post Reply
funcoolio
New user
New user
Posts: 7
Joined: 2015-04-03 09:01

HM10044: Error while executing SQL Statement

Post by funcoolio » 2015-04-03 09:17

Hello,
i am trying to upgrade from HMS 5.5.2-B2129 to 5.6.2-B2234 (but the error comes out whenever i try to upgrade from 5.5.2-B2129 to 5.6.x) when the installer starts to upgrade the database it fires up the following error:

update hm_settings set settingstring = '..........' where settingname = 'sslcipherlist' and settingstring='';
microsoft ole db provider for sql server
invalid column name 'settingname'

'........' contains a string which is too hard to rport here.

i've checked the database; there is the hm_settings table and there is the column settingname.
any idea?

HMS is running on a w2k8 box 64 bit
DB is MSSQL 2005 on a different box w2k8 64bit
both of them are virtual

User avatar
martin
Developer
Developer
Posts: 6834
Joined: 2003-11-21 01:09
Location: Sweden
Contact:

Re: HM10044: Error while executing SQL Statement

Post by martin » 2015-04-03 13:10

That sounds really odd. Can you check if the case is the same - is the column name in lowercase as well?

You can run the script manually using SQL Server Management Studio as well, but it should not be any issue running it as a part of the upgrade.
Martin Knafve
martin@hmailserver.com
https://twitter.com/knafve

funcoolio
New user
New user
Posts: 7
Joined: 2015-04-03 09:01

Re: HM10044: Error while executing SQL Statement

Post by funcoolio » 2015-04-03 13:43

i am sorry i didn't write all the senteces in their proper case

this is the table definition:

USE [hmailsrv]
GO
/****** Object: Table [dbo].[hm_settings]
SET ANSI_NULLS ON
GO
SET QUOTED_IDENTIFIER ON
GO
CREATE TABLE [dbo].[hm_settings](
[settingid] [int] IDENTITY(1,1) NOT NULL,
[settingname] [nvarchar](30) NOT NULL,
[settingstring] [nvarchar](4000) NOT NULL,
[settinginteger] [int] NOT NULL,
CONSTRAINT [hm_settings_pk] PRIMARY KEY NONCLUSTERED
(
[settingid] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY],
CONSTRAINT [u_settingname] UNIQUE NONCLUSTERED
(
[settingname] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY]
) ON [PRIMARY]

this is the error:
Image

the error reports filed names with capital letters but afaik sql do not have problem on fields name written in different cases

User avatar
SorenR
Senior user
Senior user
Posts: 3211
Joined: 2006-08-21 15:38
Location: Denmark

Re: HM10044: Error while executing SQL Statement

Post by SorenR » 2015-04-03 14:04

From what I can see then case sensitivity depend on the collate used...

MySQL is different from MSSQL, here it depends on the OS :roll:

Anyways... Try this: "SELECT CASE WHEN 'A' = 'a' THEN 'NOT CASE SENSITIVE' ELSE 'CASE SENSITIVE' END" :|
SørenR.

“With age comes wisdom, but sometimes age comes alone.”
- Oscar Wilde

funcoolio
New user
New user
Posts: 7
Joined: 2015-04-03 09:01

Re: HM10044: Error while executing SQL Statement

Post by funcoolio » 2015-04-07 12:45

SorenR wrote:From what I can see then case sensitivity depend on the collate used...

MySQL is different from MSSQL, here it depends on the OS :roll:

Anyways... Try this: "SELECT CASE WHEN 'A' = 'a' THEN 'NOT CASE SENSITIVE' ELSE 'CASE SENSITIVE' END" :|
Thank you SorenR, you opened my mind, i solved the problem by changing the database collation.

Post Reply