Help - Search - Members
Full Version: unable to login to adminkit
Kaspersky Lab Forum > English User Forum > Protection for Small and Medium Businesses
conslider
Hi All ,

I have this customer who is using the adminkit 6.0.1405... it was running perfect for some time. But recently , there is a problem. The customer could not login to the adminkit. I suggested the customer to create the backup of adminkit , install a fresh copy and restore.
But the customer could no even do the backup .. see below for backup log :

Starting klbackup utility
Initializing DCOM...OK
Initializing basic libraries...OK
Checking arguments...OK
Openning SCM...OK
Stopping service 'KLNagent'...OK
Stopping service 'CSAdminServer'...OK
Checking backup paths...OK
Acquiring SQL server connection name and DB name...OK
Connecting to the database server...FAILED - error code 1950 ('Generic db error: "Database error: code = 0x80004005, message='Unspecified error', description='Cannot open database requested in login 'KAV'. Login fails.', source='Microsoft OLE DB Provider for SQL Server', GUID='{0C733A8B-2A1C-11CE-ADE5-00AA0044773D}', LastStatement=''"')
Starting service CSAdminServer...OK
Starting service KLNagent...OK


Also in event viewer , there is error regarding the database. How could i solve this issue? I have no database trouble shoot experience ... could any of you guru's help me solve this case?

Thankyou.
Lashchenkov
QUOTE(conslider @ 25.06.2008 14:15) *
Hi All ,

I have this customer who is using the adminkit 6.0.1405... it was running perfect for some time. But recently , there is a problem. The customer could not login to the adminkit. I suggested the customer to create the backup of adminkit , install a fresh copy and restore.
But the customer could no even do the backup .. see below for backup log :

Starting klbackup utility
Initializing DCOM...OK
Initializing basic libraries...OK
Checking arguments...OK
Openning SCM...OK
Stopping service 'KLNagent'...OK
Stopping service 'CSAdminServer'...OK
Checking backup paths...OK
Acquiring SQL server connection name and DB name...OK
Connecting to the database server...FAILED - error code 1950 ('Generic db error: "Database error: code = 0x80004005, message='Unspecified error', description='Cannot open database requested in login 'KAV'. Login fails.', source='Microsoft OLE DB Provider for SQL Server', GUID='{0C733A8B-2A1C-11CE-ADE5-00AA0044773D}', LastStatement=''"')
Starting service CSAdminServer...OK
Starting service KLNagent...OK
Also in event viewer , there is error regarding the database. How could i solve this issue? I have no database trouble shoot experience ... could any of you guru's help me solve this case?

Thankyou.


Hello!

First of all, what kind of database did you use - MSDE or MS SQL Server? Do you have any database management tools like Query Analizer, etc.?
I guess we need compressed "%ProgramFiles%\Common Files\Laspersky Lab\Settings" folder from your AdminKit server computer (you may send it to me as a personal message).

Best regards,
Andrew Lashchenkov
Lashchenkov
By the way, isn't your database marked as SUSPECT? Please check your SQL server ERRORLOG and/or look through the events in EventLog.

Best regards,
Andrew Lashchenkov
conslider
Lashchenkov,

I have send a message to you , please read it , it has the information on the log file that you requested.

thankyou.
Lashchenkov
QUOTE(conslider @ 27.06.2008 08:28) *
Lashchenkov,

I have send a message to you , please read it , it has the information on the log file that you requested.

thankyou.


Look at your SQL server errorlog:

2008-05-20 12:19:14.09 spid51 Starting up database 'KAV'.
2008-05-20 12:19:14.10 spid51 Bypassing recovery for database 'KAV' because it is marked SUSPECT.

So, you have got some database phisical corruption. First of all, to prevent such problams in future, be sure to disable hardware write caching option in the harddrive properties on your database server computer - this is the most usual reason of such problems.

Try to fix the problem using standard database management tools (see more here: sp_resetstatus, DBCC CHECKDB, FIX: A database is marked suspect when you open the database in SQL Server 2000, and just look for "it is marked SUSPECT" in google if you need some more info about the stuff).

Probably you should also check you hard disk.

If you fail to recover your database, you will have to re-install AdminKit and databse and restore from backup (created by klbackup.exe or AdminKit Backup task), if you have one...

Best regards,
Andrew Lashchenkov
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2009 Invision Power Services, Inc.