You’re offline. This is a read only version of the page.
95
Hallo,
nach dem Upgrade von 9.0 auf 9.1 incl. Pack 9.1.6.3 erhalten wir, wenn ein Benutzer der Verkaufschance als Stakeholder hinzufügt wird folgende Fehlermeldung.
Exception: Invalid object name 'ScaleGroup'. Exception: System.Data.SqlClient.SqlException: Invalid object name 'ScaleGroup'. >
But the user is added after the error confirmation.
Does anyone have a solution approach to fix the error or suppress the error message.
Thanks & greetings
Patrick
Exception when executing query: SELECT Id, [ConnectionString], [DatabaseName], [ExternalSdkEndpoint], [HelpContentServerUrl], [InternalSdkEndpoint], [MirroredSqlServerName], [Name], [PartitionNumber], [PodId], [ProvisioningAffinityGroupId], [ProvisioningState], [ReportServerUrl], [ScaleGroupWebStoreName], [SqlServerName], [State], [StatsScaleGroupWebStoreName], [UniqueifierId], [WebApplicationUrl], [WebStoreName], [WitnessServerId] FROM [ScaleGroup] WHERE ((([Id] = @Id0)) ) Exception: Invalid object name 'ScaleGroup'. Exception: System.Data.SqlClient.SqlException: Invalid object name 'ScaleGroup'. > at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction) +0x5e > at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose) +0x17c > at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady) +0x0 > at System.Data.SqlClient.SqlDataReader.TryConsumeMetaData() +0x40 > at System.Data.SqlClient.SqlDataReader.get_MetaData() +0x3c > at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString, Boolean isInternal, Boolean forDescribeParameterEncryption, Boolean shouldCacheForAlwaysEncrypted) +0xf3 > 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) +0x65b > 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) +0x2a0 > at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) +0x19 > at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) +0x67 > at Microsoft.Crm.CrmDbConnection.LockConnectionAndExecuteMethod[TResult](IDbConnection connection, Func`1 executeMethod) +0x56 > at Microsoft.Crm.CrmDbConnection.InternalExecuteWithRetry[TResult](Func`1 ExecuteMethod, IDbCommand command, ICrmTransaction crmTransaction) +0x71 > at Microsoft.Crm.CrmDbConnection.<>c__DisplayClass157_0.b__0() +0xd0 > at Microsoft.PowerApps.CoreFramework.ActivityLoggerExtensions.Execute[TResult](ILogger logger, EventId eventId, ActivityType activityType, Func`1 func, IEnumerable`1 additionalCustomProperties) +0x91 > at Microsoft.Xrm.Telemetry.XrmTelemetryExtensions.Execute[TResult](ILogger logger, XrmTelemetryActivityType activityType, Func`1 func) +0x0 > at Microsoft.Crm.CrmDbConnection.InternalExecuteReader(IDbCommand command, Nullable`1 commandBehavior, ICrmTransaction crmTransaction, Int32 sourceLineNumber, String memberName, String sourceFilePath) +0x48 > at Microsoft.Crm.CrmDbConnection.ExecuteReader(IDbCommand command, Boolean impersonate, Int32 sourceLineNumber, String memberName, String sourceFilePath) +0x9 > at Microsoft.Crm.SharedDatabase.DatabaseService.ExecuteBaseReader(CrmDbConnection connection, IDbCommand command, String[] columns, IDictionary collectionToFill) +0x1e
Hello unfortunately the bug was not fixed in the version 9.1.7.5. Is there any news regarding this bug or does anyone have a solution`?
This appears to be an ongoing issue with v9.1 on premise environments, as the object names they are referring to are for online. We do have an internal investigation and working to get this resolved in a future update. It appears that the last build of 9.1.6.3 did not include the fix. You can open a service request ticket if you need more information.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (