Showing posts with label sp2. Show all posts
Showing posts with label sp2. Show all posts

Thursday, March 29, 2012

error 18456 when trying to connect to 2005 using odbc

Hi all

I am using Windows XP SP2 with a Sql server 2005 Express installation. I created a test db with a user called test, schema also test. I gave the permission connect, db_datareader and db_datawriter. I can now connect into this user using WinSQL. But if I want to connect using a application which is using ODBC, then I get the error:

[SQLSTATE=28000 - [Microsoft][SQL Native][SQL Server]Login failed for user 'test'.[Native Error=18456]]

Because I connect using ODBC, I think there must be the problem. But I have to connect with ODBC. There is no other possibility.

any ideas ?

Regards, Waff

I found this out:

The server collation is defined to: Latin1_General_CI_AS

If I create a new login id in lowercase, then ODBC will change it to uppercase and then the server refuse the access. But why. CI means case insensitive, so doesn't matter if upper or lower case. should.

How do you use a id in lowercase and connecto via ODBC ?

You need to enable TCP in order for ODBC clients to connect. Check out http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx for information about doing this.

Mike

|||

Guess has something to do with the collation. I used Latin1_General_AI_CI.

If I create my login id in lowercase and try then to connect to the db using ODBC, then ODBC will switch my id to uppercase and so I can't logon.

Anyway, somehow, it must be possible to modify the server settings, so that it doesn't matter how I logon. lowercase or uppercase. I tryed with CI and CS but still them same.

ODBC is enabled but think has to do with the collation.

What are you using if you use id's as upper/lower case as Test ?

error 18456 when trying to connect to 2005 using odbc

Hi all

I am using Windows XP SP2 with a Sql server 2005 Express installation. I created a test db with a user called test, schema also test. I gave the permission connect, db_datareader and db_datawriter. I can now connect into this user using WinSQL. But if I want to connect using a application which is using ODBC, then I get the error:

[SQLSTATE=28000 - [Microsoft][SQL Native][SQL Server]Login failed for user 'test'.[Native Error=18456]]

Because I connect using ODBC, I think there must be the problem. But I have to connect with ODBC. There is no other possibility.

any ideas ?

Regards, Waff

I found this out:

The server collation is defined to: Latin1_General_CI_AS

If I create a new login id in lowercase, then ODBC will change it to uppercase and then the server refuse the access. But why. CI means case insensitive, so doesn't matter if upper or lower case. should.

How do you use a id in lowercase and connecto via ODBC ?

You need to enable TCP in order for ODBC clients to connect. Check out http://blogs.msdn.com/sqlexpress/archive/2004/07/23/192044.aspx for information about doing this.

Mike

|||

Guess has something to do with the collation. I used Latin1_General_AI_CI.

If I create my login id in lowercase and try then to connect to the db using ODBC, then ODBC will switch my id to uppercase and so I can't logon.

Anyway, somehow, it must be possible to modify the server settings, so that it doesn't matter how I logon. lowercase or uppercase. I tryed with CI and CS but still them same.

ODBC is enabled but think has to do with the collation.

What are you using if you use id's as upper/lower case as Test ?

Friday, March 9, 2012

error 0xE0040200 when browse a cube

I am using AS 2005 + SP2.

I got error 0xE0040200 when browse a cube with a calculation member for a dimension, the calculation is defined like the following.

iif([Time].[Calendar].currentmember.prevmember is null or
([TimeSeries].[Period].&[1], [Time].[Calendar].currentmember.prevmember) = 0, null, ROUND(((([TimeSeries].[Period].&[1],
[Time].[Calendar].currentmember) -
([TimeSeries].[Period].&[1], [Time].[Calendar].currentmember.prevmember))/([TimeSeries].[Period].&[1], [Time].[Calendar].currentmember.prevmember)),4))'

I think the problem is around "([TimeSeries].[Period].&[1], [Time].[Calendar].currentmember.prevmember) = 0", because when I change the "=0" to "is null", the error disappears.

Can anyone know why the "=0" won't work? BTW, the same calculation works well in AS 2000.

Thanks

It seems that it is a bug of cube browser in AS 2005.

When I browse the cube in Excel with AS 9.0 OLE DB provider, everything is fine.

has anyone experienced the same?

Thanks
Michael

Wednesday, March 7, 2012

Error 0x80041010 WinMgmt when launching SQL SERVER MANAGEMENT STUD

Hi:
SQL 2005 sp2 is already release. Just like to know if this error
0x80041010 have already been fixed in SP2 of SQL 2005.
In the list of bugs fixed by SP2 the error 0x80041010 is not included,
check this site http://support.microsoft.com/kb/921896
Thanks.
*** Sent via Developersdex http://www.codecomments.com ***
I was having the same problem on my x64 box running SQL 2005 SP1 in
cluster.
What happen that somehow permissions were removed from local
administrators and DBA's group. I had to login as sa and reassign the
system admin permissions to local admin and dba's group and it start
wotking fine.
BC
*** Sent via Developersdex http://www.codecomments.com ***
|||On Apr 6, 3:37 am, Bader Cheema <bader_chee...@.hotmail.com> wrote:
> I was having the same problem on my x64 box running SQL 2005 SP1 in
> cluster.
> What happen that somehow permissions were removed from local
> administrators and DBA's group. I had to login as sa and reassign the
> system admin permissions to local admin and dba's group and it start
> wotking fine.
> BC
> *** Sent via Developersdexhttp://www.codecomments.com***
Hi,
I tried your solution but can't understand what you mean.
what do you mean by local administrators? BUILTIN\Administrators? it
already has sysadmin in server roles.
and I didn't find DBA's group in my SQL configuration.
Please elaborate your solution for me.
I didn't install SQL 2005 SP2 yet.
Does it solve this problem?
Thanks in advance.