GSDBSet ODBC Connect Fail (Not a regular .reg issue)

[LeDude]

I've seen other tutorials, but it's not a simple .reg issue, i've tried everything and still get this error msg.

I'm using Windows 7 (64bit) and MSSQL 2008 R2.

I've tried enabling ODBC connection for SQL Server/SQL Server Native Client 10.0, with both Integrated authentication and using SQL acc authentication.
I've tried creating a Mu login on the sql, gave it all the access permissions to the Mu database files and configured on both server and ODBC, still the same error.
I've tried turning off firewall/UAC is already off, Windows XP compatibility, still nothing.
I've added these changes on Both ODBCs, normal one and SysWOW64 one.

I simply don't know what else to do.

The only thing i know is that the regular .reg file that comes with it cannot connect to the database (Seems like NT authentication doesn't work).

It's not an ODBC, connection or computer problem, because i run a server of another game (using ODBC with SQL Server Native Client 10.0) without any problems.

Anyone would have any idea on what i could possibly missing? This is extremely frustrating!

[MentaL]

[DragonSeth]

1.first do the .reg 64 bit
2.run server admin

[LeDude]

As i clearly stated it's not something as simple as that.

However, i might have found what it was. For some reason it was identifying the \\PW as part of the password.
Now i'm trying to figure how to get the JoinServer to open, and no, it's not just adm/compatibility.

[DragonSeth]

add me on skype divintyevolution

[KarLi]

You gotta add the odbc manually l earn that and you will never have a problem (from data sources)

[LeDude]

I already did. I use a mixed SQL Database, with sa/PW, i used the account authentication method, it was still failing until i remove the \\PW line on the config, anyway, i think i fixed that, just can't open JoinServer at all now...

[KarLi]

If you can't run joinserver it means you haven't fixed it ...
restore original databases i suggest and maybe use sql 2000? easier etc.

also in odbc.req u must put SQLEXPRESS/YOUR-PC-NAME instead of (local) on win 2008 and run it.