ADVANCED TOPIC - CONTACT YOUR APPRENDA REPRESENTATIVE FOR SUPPORT RESOLVING THIS ISSUE.
A user reported an issue promoting an application, below is the error message found in the SOC:
Event Log Details
Timestamp: 09/24/2014 12:59:31 PM
Application: Storage Controlling Services Version 1 4cffcc32-3d96-41c2-8263-1017fc958f9a
SessionId: 78cc450a-ec43-e411-9411-0050560115d7
SessionActive: false
InstanceId: ccefa2da-335e-403c-8211-38b7ac21cc6e
ProviderName: Apprenda, Inc 00000000-0000-4000-0000-000000000001
Tenant: Tenant for Storage Controlling Services a6a4a17b-12d9-e211-be75-002522f83bab
Error event created by Apprenda.SaaSGrid.Data.Services.StorageManager from machine.
-----------------LogMessage-----------------
Error occurred adding binding tenant with id '7b33669b-2073-48d1-a0c8-8dba5bdfb33f' to application with id '94d491b2-fc43-e411-9411-0050560115d7' for provider '7b33669b-2073-48d1-a0c8-8dba5bdfb33f
-----------------EndLogMessage-----------------
-----------------SurfaceException (System.Exception)-----------------
A PersistencePartition must exist before it can be linked with a user shard.
at Apprenda.SaaSGrid.Data.PersistenceLoginRepository.CreateHelper(PersistencePartition owningPartition, PersistenceLogin existingLogin)
at Apprenda.SaaSGrid.Data.PersistenceLoginRepository.Create(PersistencePartition owningPartition, PersistenceLogin login, Boolean propagateTransactionScope)
at Apprenda.SaaSGrid.Data.AbstractProviderPersistenceManager.CreateTenantLoginToProviderDB(PersistenceLogin login)
at Apprenda.SaaSGrid.Data.AbstractProviderPersistenceManager.GrantTenantAccessToSharedTables(PersistenceLogin login)
at Apprenda.SaaSGrid.Data.CommingledTDP.CreateLoginAndGrantAccess(IDatabase database)
at Apprenda.SaaSGrid.Data.CommingledTDP.Bind(TenantBindInstruction instruction)
at Apprenda.SaaSGrid.Data.Services.StorageManager.CreateTenantPartition(BasicDataPartitionParametersDTO sourceParameters, SaaSGridGuid tenantId, TenantBindInstructionDTO instruction)
-----------------EndSurfaceException-----------------
-----------------TransactionInformation-----------------
Isolation Level:ReadUncommitted
Status:Active
Creation Time:24.09.2014 16:56:33
Distributed Identifier:69eea416-44f4-402f-8dee-23392e8fdd87
Local Identifier:5b8da185-6cf9-4608-9e9a-cd8f8e04890d:32
-----------------EndTransactionInformation-----------------
Cause
The issue was caused by a left-behind provider database on the SQL Server being used by the platform.
Resolution
To resolve the issue, log in to the SQL Server being targeted for deployment of this application and search for a left behind provider database. You will be able to identify the offending DB since every Apprenda deployed DB comes in pairs
appalias_guid
appalias_provider
In this particular case, the server will only have a provider DB but not its matching pair.
Comments