[SOLVED]Unable to login to otrs

[kool_kid]

I'm getting this error when trying to login to otrs

Error Message: Sorry, can't load C:\inetpub\wwwroot\otrs::Kernel::Language::en_ITSMConfigItem.pm

Error Details
Backend ERROR: OTRS-CGI-10 Perl: 5.12.3 OS: MSWin32 Time: Tue May 24 19:31:44 2011

Message: Sorry, can't load C:\inetpub\wwwroot\otrs::Kernel::Language::en_ITSMConfigItem.pm! Check the C:\inetpub\wwwroot\otrs::Kernel::Language::en_ITSMConfigItem.pm (perl -cw)!

Traceback (1708):
Module: Kernel::Language::new (v1.77) Line: 169
Module: Kernel::Output::HTML::Layout::new (v1.350) Line: 156
Module: Kernel::System::Web::InterfaceAgent::Run (v1.58) Line: 142
Module: C:\Inetpub\wwwroot\otrs\bin\cgi-bin\index.pl (v1.89) Line: 45

The logins were working properly from last 4 months. I'm using otrs on Windows 2003 Server, otrs is integrated to AD and using MSSQL backend. otrs version is 3.0.5

I have checked for that en_ITSMConfigItem.pm file and it exist. The permissions on the file are same as any other file.

[kool_kid]

The problem is here

DBI connect('driver={SQL Server};Server=192.168.62.16,1433;database=otrs;uid=otrs;pwd=password;','otrs',...) failed: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. (SQL-08001) [state was 08001 now 01000]
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). (SQL-01000) at C:/Inetpub/wwwroot/otrs/Kernel/System/DB.pm line 210
ERROR: OTRS-otrs.CheckDB.pl-10 Perl: 5.12.3 OS: MSWin32 Time: Tue May 24 19:49:16 2011

Message: [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied. (SQL-08001) [state was 08001 now 01000]
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect()). (SQL-01000)

Traceback (5560):
Module: Kernel::System::DB::new (v1.127) Line: 181
Module: C:\Inetpub\wwwroot\otrs\bin\otrs.CheckDB.pl (v1.3) Line: 52

No database connect!

I checked the connectivity of OBDC driver from the server it says "tested successfully"

Any pointers anyone?

[kool_kid]

The service called "SQL Browser Service" was stopped. Starting this service fixed the problem.