LNSS 8 and MS SQL 2005 problem (Full Version)

All Forums >> [Networking & Security] >> GFI LANguard



Message

VictorC -> LNSS 8 and MS SQL 2005 problem (7.Aug.2008 8:23:23 AM)

Hello,
i've just installed LNSS 8 eval. and run into strange problem, during installation i've entered to use SQL server to store scan results, entered sa login and everything was working, LNSS created new database named LNSSScanResults BUT, everytime i run ANY scan type it just says: The application could not connect to database!" and now "Inavalid object name 'Scans'". I am connecting to (local) database using sa user with full access rights.
Any idea whats wrong?
Thank you for help!
VicC

here is complete debug scan log file
http://rapidshare.com/files/135489823/lanss_v8_securityscanner.zip.html



DrewE -> RE: LNSS 8 and MS SQL 2005 problem (7.Aug.2008 11:00:11 AM)

Can you set the Configuration -> Database Maintenance Operations to use MS Access instead of SQL?  Does this work successfully?  You can also try creating a new login within SQL Studio which has SysAdmin privileges. When creating the new login, ensure you disable enforcing password policies, and ensure it is a SQL login and not a windows login.



VictorC -> RE: LNSS 8 and MS SQL 2005 problem (7.Aug.2008 11:19:12 AM)

I just tryied to change to ms access and error is the same:
"Failed to create the database on remote SQL server, Possible reasons: timeout or user does not have sufficient credentials"

So i created new user gfidbadmin sysadmin ticked and password policies unticked and problem is still the same:
"Failed to create the database on remote SQL server, Possible reasons: timeout or user does not have sufficient credentials"

no errors in windows app eventlog



DrewE -> RE: LNSS 8 and MS SQL 2005 problem (7.Aug.2008 11:24:53 AM)

Try stopping the GFI Languard Network Security Scanner service first, then repeating the switch to MS Access database backend.  



VictorC -> RE: LNSS 8 and MS SQL 2005 problem (7.Aug.2008 11:28:52 AM)

It didnt helped, I stopped the service manually and switched to ms access option, pressed OK and:
"Failed to create the database on remote SQL server, Possible reasons: timeout or user does not have sufficient credentials"



VictorC -> RE: LNSS 8 and MS SQL 2005 problem (7.Aug.2008 11:39:52 AM)

I just installed LNSS on different pc and it works with sql !!! so problem is only when trying to connect to (local) ms access/sql database... any idea how to fix it?



VictorC -> RE: LNSS 8 and MS SQL 2005 problem (7.Aug.2008 3:16:24 PM)

Any way to diagnose what is wrong when conecting localy to db? When using debug enabled this is resul:
http://rapidshare.com/files/135489823/lanss_v8_securityscanner.zip.html

quote:

2008-08-07,10:53:34,338,3,"#000000b0","#000008a0","info","ServiceProvider","Adding the scan 105331400 to the database..."
2008-08-07,10:53:34,354,3,"#000000b0","#000008a0","info","ServiceProvider","TDbCommon.Open table (Scans) to 0"
2008-08-07,10:53:34,354,3,"#000000b0","#000008a0","info","ServiceProvider","TDbCommon.Open  Požadované vlastnosti nelze podporovat"
2008-08-07,10:53:34,354,1,"#000000b0","#000008a0","error","ServiceProvider","TDbCommon.Open  Požadované vlastnosti nelze podporovat"
2008-08-07,10:53:34,416,3,"#000000b0","#000008a0","info","ServiceProvider","QRYScans.Open SQL (select [ScansId] from [Scans]where [Session] = '105331400'  ) to 0"
2008-08-07,10:53:34,416,1,"#000000b0","#000008a0","error","ServiceProvider","TDBCache.Locate error Invalid object name 'Scans'-retrying operation"
2008-08-07,10:53:34,525,3,"#000000b0","#000008a0","info","ServiceProvider","QRYScans.Open SQL (select [ScansId] from [Scans]where [Session] = '105331400'  ) to 100"
2008-08-07,10:53:34,525,1,"#000000b0","#000008a0","error","ServiceProvider","TDBCache.Locate error Invalid object name 'Scans'-retrying operation"



DrewE -> RE: LNSS 8 and MS SQL 2005 problem (8.Aug.2008 9:17:27 AM)

Victor,

Does this work:

A. Open ODBC Data Sources
    1. -Click button Windows 'Start'
    2. -Select from list 'Control Panel'
    3. -Double click on icon 'Administrative Tools'
    4. -Double click on icon 'Data Sources (ODBC)'

B. -Register your database
    1. -Select tab 'System DSN'
    2. -Click button 'Add'

C. -Select your driver
        1. -Select from list 'Sql Server'
        2. -Click button 'Finish'

D. -Fill in the data
        1. Choose the real database name of for your database
        2. Fill in possibly a description
        3. Choose which SQL server you want to connect to
           (you might have to start your Microsoft SQL server first so
            that it can be found when you click on the list, and or
            install it on your local machine, if not already done)

             e.g. <yoursqlservername>

            e.g. TEST

           (e.g. the name of the Microsoft SQL server
            installed on your computer, to see which name,
            hold e.g. your cursor above the Microsoft SQL server
            name on the taskbar) or you can skip the name if you are working   locally, by using (local)

        4. -In the screen 'How should SQL Server verify the authenticity of the login ID?'

            i. -Enable radio button 'With SQL Server authentication
                using a login ID and password entered by the user'

            ii. -Enable checkbox 'Connect to SQL Server to obtain default
                settings for the additional configuration options'

                1. Enter a 'Login ID'
                    e.g.
                     sa

                2. Enter a password

         5. -Click button 'Next'
         6. -Enable checkbox 'Change the default database to'
                1. -Select from list the database created for GFI

E. -Click button 'Next'

F. -Click button 'Finish'

            You should now see information similar to
            the following:

--- cut here: begin --------------------------------------------------

Microsoft SQL Server ODBC Driver Version 03.81.9042

Data Source Name: northwind
Data Source Description: test
Server: (local)
Database: (Default)
Language: (Default)
Translate Character Data: Yes
Log Long Running Queries: No
Log Driver Statistics: No
Use Integrated Security: Yes
Use Regional Settings: No
Prepared Statements Option: Drop temporary procedures on disconnect
Use Failover Server: No
Use ANSI Quoted Identifiers: Yes
Use ANSI Null, Paddings and Warnings: Yes
Data Encryption: No

--- cut here: end ----------------------------------------------------

        7. Test, by clicking
            button 'Test Data Source'
            If should show information similar
            to the following:

--- cut here: begin --------------------------------------------------

Microsoft SQL Server ODBC Driver Version 03.81.9042

Running connectivity tests...

Attempting connection
Connection established
Verifying option settings
Disconnecting from server

TESTS COMPLETED SUCCESSFULLY!

--- cut here: end ----------------------------------------------------

3. -You should now see that in the tab 'System DNS'
    your database name (e.g. 'northwind') has been added

4. -Click button 'OK'

(These instructions are taken and modified from the following source: http://www.faqts.com/knowledge_base/view.phtml/aid/33020/fid/147)



VictorC -> RE: LNSS 8 and MS SQL 2005 problem (8.Aug.2008 9:28:03 AM)

yes, this is working, every single step from your post works just fine, at the end i've got result:
TESTS COMPLETED SUCCESSFULLY!



DrewE -> RE: LNSS 8 and MS SQL 2005 problem (8.Aug.2008 9:36:50 AM)

Will you please tell me what the collation mode of your SQL server is?  Typically you can find it by right clicking the very first node within SQL Enterprise Manager or SQL Studio



VictorC -> RE: LNSS 8 and MS SQL 2005 problem (8.Aug.2008 9:45:17 AM)

My server collation is Czech_CI_AS



VictorC -> RE: LNSS 8 and MS SQL 2005 problem (11.Aug.2008 5:23:42 AM)

any idea?



DrewE -> RE: LNSS 8 and MS SQL 2005 problem (11.Aug.2008 9:39:01 AM)

I have not tested this collation mode.  Typically our products are tested with SQL_Latin1_CI_AS.  Your software is correctly using the 'CI = Case Insensitive' which is great, however the remainder of the collation mode may be causing this trouble.  I would recommend confirming this with us by opening a support ticket at http://support.gfi.com



VictorC -> RE: LNSS 8 and MS SQL 2005 problem (11.Aug.2008 9:51:20 AM)

I just tried to install report pack for lnss, during installation choosed SQL and here is another error:
quote:

 
08/11/08 15:48:44: CheckDbStructureSQLServer(MYSERVER, sa, C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\pluginDBStruct.xml)
08/11/08 15:48:44: CSQLDatabase::Exists LNSSScanResults on server MYSERVER
08/11/08 15:48:44: CSQLDatabase::Exist  Create connection
08/11/08 15:48:44: CSQLDatabase::Exist  Open connection.
08/11/08 15:48:44: CSQLDatabase::Exist  Close connection returned (0).
08/11/08 15:48:44: CSQLDatabase::GetConnectionString In
08/11/08 15:48:44: CSQLDatabase::GetConnectionString Out
08/11/08 15:48:45: CTableDef::Connect  Create the ADODB objects.
08/11/08 15:48:45: CTableDef::Connect  Failed to create Table object
08/11/08 15:48:45: CheckTablesStructure Failed to connect the ADOX table -2147221164.
08/11/08 15:48:45: CheckDbStructureSQLServer  Check failed for database (LNSSScanResults).


i try to change collation...



VictorC -> RE: LNSS 8 and MS SQL 2005 problem (11.Aug.2008 10:02:38 AM)

Collation is not the problem, i changed it to SQL_Latin1_CI_AS and lnss still not working and as i wrote before (http://forums.gfi.com/fb.aspx?m=900766767), i am able to use the same db from another pc with lnss whitch is connecting to it remotely. Only when connecting to that db localy, lnss isnt working!



Page: [1] 2   next >   >>