Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
keine Credentials nach Update 2017 auf 2022 vorhanden
#1
Hallo,

nach dem Update von Version 2017 auf die neueste Version 2022 sind leider keine gespeicherten Credentials mehr vorhanden. Zudem erscheinen nach dem ersten Start der aktualisierten Anwendung SQL-Fehler:

==================================================

 Message;Timestamp;Type;Details
UserGetAll;28.02.2022 14:42:18;Error;"An error occured on executing an sql statement
UserGetAll
Invalid attempt to call Read when reader is closed.

---------------------------

  at System.Data.SqlClient.SqlDataReader.TryReadInternal(Boolean setTimeout, Boolean& more)
  at System.Data.SqlClient.SqlDataReader.Read()
  at CloudAdminDataAccess.SqlDataAccessor.ConsoleUserGetAll()
"
LogsAdd;28.02.2022 14:42:16;Error;"An error occured on executing an sql statement
LogsAdd
There is already an open DataReader associated with this Command which must be closed first.

---------------------------

  at System.Data.SqlClient.SqlInternalConnectionTds.ValidateConnectionForExecute(SqlCommand command)
  at System.Data.SqlClient.SqlConnection.ValidateConnectionForExecute(String method, SqlCommand command)
  at System.Data.SqlClient.SqlCommand.ValidateCommand(String method, Boolean async)
  at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
  at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
  at CloudAdminDataAccess.SqlDataAccessor.LogsAdd(LogItem logItem)
"
;28.02.2022 14:42:16;Error;"An error occured on executing an sql statement
ExtraTag

---------------------------

  at System.Data.ProviderBase.FieldNameLookup.GetOrdinal(String fieldName)
  at System.Data.SqlClient.SqlDataReader.GetOrdinal(String name)
  at CloudAdminDataAccess.SqlDataAccessor.HasColumnAndNotDbNull(SqlDataReader r, String columnName)
"
UserGetId;28.02.2022 14:42:15;Error;"An error occured on executing an sql statement
UserGetId
Procedure or function UserGetId has too many arguments specified.

---------------------------

  at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
  at System.Data.SqlClient.SqlInternalConnection.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.SqlDataReader.TryConsumeMetaData()
  at System.Data.SqlClient.SqlDataReader.get_MetaData()
  at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted)
  at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, Boolean inRetry, SqlDataReader ds, Boolean describeParameterEncryptionRequest)
  at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean& usedCache, Boolean asyncWrite, Boolean inRetry)
  at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
  at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
  at System.Data.SqlClient.SqlCommand.ExecuteReader()
  at CloudAdminDataAccess.SqlDataAccessor.InitializeUser(String username, String domain, String sid, Int32 type, String extraTag)
"

49.281898
8.404917


==================================================
Bei einer Recherche hier im Forum bin ich auf ähnliche Probleme von anderen Usern gestoßen. In einem Beitrag wurde beschrieben, wie man das DB-Update händisch anstößt und fehlende Tabellen/Spalten hinzufügt (ASG_DBUpdate, Dateien: StoredProcs.txt, Update.txt). Daraufhin sind die SQL-Fehler verschwunden, die Credentiuals leider immer noch nicht da.

Ich bitte um Unterstützung! Vielen Dank vorab...
Reply


Messages In This Thread
keine Credentials nach Update 2017 auf 2022 vorhanden - by bknopp - 07-04-2022, 08:21 AM



Users browsing this thread: 1 Guest(s)