This project is read-only.
1
Vote

Error importing BLG on Windows 7 SQL2008

description

Getting the following error at the stage of importing the BLG. It seems to process it fine but then comes up with the database connection failure:
 
SQLNexus Information: 0 : BLG Blaster (Perfmon/Sysmon BLG files) is a INexusImporter
 
DateTime=2011-03-09T12:27:15.5617946Z
 
SQLNexus Information: 0 : Loading PSSDIAG.BLG
 
DateTime=2011-03-09T12:27:15.6227946Z
 
SQLNexus Information: 0 : Loading PSSDIAG1.BLG
 
DateTime=2011-03-09T12:30:40.6357946Z
 
SQLNexus Critical: 0 : Exception: Cannot open database "sqlnexus" requested by the login. The login failed.
 
Login failed for user 'DOMAIN\user'.. Source: .Net SqlClient Data Provider. Stack: at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
 
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
 
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
 
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
 
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
 
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
 
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
 
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
 
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
 
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
 
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
 
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
 
at System.Data.SqlClient.SqlConnection.Open()
 
at PerfmonImporter.BLGImporter.TotalRows() in C:\temp\nexus\sqlnexus_codeplex\PerfmonImporter\BLGImporter.cs:line 199
 
at PerfmonImporter.BLGImporter.DoImport() in C:\temp\nexus\sqlnexus_codeplex\PerfmonImporter\BLGImporter.cs:line 305
 
at sqlnexus.fmImport.DoImport() in C:\temp\nexus\sqlnexus_codeplex\sqlnexus\fmImport.cs:line 642. InnerException: .
 
DateTime=2011-03-09T12:33:02.9117946Z
 
SQLNexus Information: 0 : Import failed. (637 sec, 2664181 rows inserted)

comments

amitban wrote Mar 9, 2011 at 1:19 PM

Can you check the State number for the login failed message in the SQL Errorlog? At this point, it looks like the Nexus database was unaccessibled by the application due to which the error was reported. Profiler trace captured during the import might help narrowing down the issue.

bimaldave wrote Mar 14, 2011 at 6:18 PM

Hi, this is the logon error:

Date 2011-03-14 17:14:52
Log SQL Server (Current - 2011-03-10 10:20:00)

Source Logon

Message
Error: 18456, Severity: 14, State: 38.

amitban wrote Mar 23, 2011 at 9:41 PM

State 38 corresponds to "Failed to open the explicitly specified database". Does your login and the SQL service account have permissions on the path where the SQL Nexus database files are stored?

bimaldave wrote Mar 24, 2011 at 7:03 PM

Yes, I checked and my account has dbo rights so it doesn't seem like its permissions related. Anything else you can think of?

amitban wrote Mar 29, 2011 at 6:10 PM

Can you drop the sqlnexus database and have Nexus recreate the same and check if the same issue occurs?

amitban wrote Mar 29, 2011 at 6:14 PM

Can you also check by collect a profiler trace with Audit Events to see which Audit is failing or throwing an error?

bimaldave wrote Mar 29, 2011 at 10:05 PM

Tried dropping the db - same error. Also enabled SQL logins, logged in as SA account but still get the same error. Very strange. I am running this on sql express but dont have profiler installed at the moment. Will install it and upload the log shortly.

bimaldave wrote Mar 29, 2011 at 10:09 PM

Interestingly I just checked the event log and found this:

A fatal error occurred while reading the input stream from the network. The session will be terminated (input error: 109, output error: 0).

It is reported by event id 4014 from SQL Server. Does that help at all?

amitban wrote Mar 29, 2011 at 11:16 PM

Yes that helps. That is a TDS stream error. What is the state number reported? Can you patch the SQL Server engine with the latest cumulative update and then check if the issue occurs? This is not an issue with SQL Nexus but a protocol related error which might need us to collect TDS related information. This would be difficult to do and out-of-scope for this dicussion forum.

jackli wrote Apr 6, 2011 at 3:05 PM

There is an issue of importing perfmon if runs under UAC. You can right click on sqlnexus.exe and "run as administrator" to make it work. there will be an update for Sql Nexus soon that will include this fix

jackli wrote Apr 6, 2011 at 3:06 PM

this is an issue when running SQL Nexus under UAC to import perfmon. Launch it as administrator (right click on sqlnexus.exe and choose "run as administrator"). Next release will include this fix that doesn't require "run as administrator".

Norberto2021 wrote Dec 21, 2011 at 2:33 PM

Hi, I had the same login error, and I found SQLNexus create DBs with "AutoClose Option = True".
Changing "AutoClose Option = False" I solved my login problem.

I hope this can help.

amitban wrote Dec 21, 2011 at 7:07 PM

I think the SQLNexus database is being created with AutoClose option set to ON because your model database has that property set. We don't explicitly set AutoClose to ON when creating a new Nexus database.

Norberto2021 wrote Dec 23, 2011 at 2:13 PM

Amitban I understand and know this is strange, but I checked the model DB and the AutoClose option is set to OFF.
When I create manualy a DB, it creates with the AutoClose option set to OFF.
However when SQLNexus creates a DB, it creates with AutoClose option set to ON.

Im using a Microsoft SQL Server 2008 (SP2) - 10.0.4000.0 (Intel X86) Sep 16 2010 20:09:22 Copyright (c) 1988-2008 Microsoft Corporation Express Edition on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)

wrote Feb 22, 2013 at 12:49 AM