NetWitness Community

kiseunglee · ‎2016-07-24

May I ask about the following ConsoleServer error log as below?

3/27/2016 11:18:36 PM

[5] System.Data.SqlClient.SqlException:

An invalid parameter or option was specified for procedure 'sys.sp_change_users_login'.

The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).

Operation cancelled by user.

The number of orphaned users fixed by updating users was 0.

The number of orphaned users fixed by adding new logins and then updating users was 0.

The number of orphaned users fixed by updating users was 0.

The number of orphaned users fixed by adding new logins and then updating users was 0.

The number of orphaned users fixed by updating users was 0.

The number of orphaned users fixed by adding new logins and then updating users was 0.

SQL Error Code: 80131904

SQL Error 15600 in sp_change_users_login(214): An invalid parameter or option was specified for procedure 'sys.sp_change_users_login'.

SQL Error 14234 in sp_verify_job(197): The specified '@owner_login_name' is invalid (valid values are returned by sp_helplogins [excluding Windows NT groups]).

SQL Error 0 in (0): Operation cancelled by user.

SQL Error 15295 in sp_change_users_login(273): The number of orphaned users fixed by updating users was 0.

SQL Error 15294 in sp_change_users_login(274): The number of orphaned users fixed by adding new logins and then updating users was 0.

SQL Error 15295 in sp_change_users_login(273): The number of orphaned users fixed by updating users was 0.

SQL Error 15294 in sp_change_users_login(274): The number of orphaned users fixed by adding new logins and then updating users was 0.

SQL Error 15295 in sp_change_users_login(273): The number of orphaned users fixed by updating users was 0.

SQL Error 15294 in sp_change_users_login(274): The number of orphaned users fixed by adding new logins and then updating users was 0.

at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)

at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)

at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)

at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader()

at System.Data.SqlClient.SqlCommand.EndExecuteNonQueryInternal(IAsyncResult asyncResult)

at System.Data.SqlClient.SqlCommand.EndExecuteNonQueryAsync(IAsyncResult asyncResult)

at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)

--- End of stack trace from previous location where exception was thrown ---

at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

at a.b.X᜛.ᜊ.ᜀ()

3/27/2016 11:18:36 PM

Exiting...

3/27/2016 11:18:36 PM

Closed.

any advice on this error message?

i can't find agent on ECAT UI

thank

MohamedEssam · ‎2016-07-25

Hi kiseung lee;

The error is not related to agent shown in ECAT UI

Please use the following pdf document to check agent server communication flow

Best Regards

Mohamed Essam

MohamedEssam · ‎2016-07-25

Hi kiseung lee

Also more information about the issue

http://www.sqlservercentral.com/Forums/Topic543186-1291-1.aspx

Best Regards

Mohamed Essam