Architect - Scripts for new db fail because of old "Asap" names

bugs
1

When a new project is created manually and the scripts should fill a new database defined in OrigamSettings, the scripts fail, because first all scripts for the Root package are executed and these already contain the renaming procedure from “Asap” to “Origam”. After that the scripts from the Security package fail because the referenced “Asap…” tables no longer exist. It starts with script 1.000/00040_Feature_NET_MEMBERSHIP_EXCLUSIVE_USE_TurnedOnForInitialDbScript (the example is from one version higher).

Error while loading package 'Security'
Update failed.
========================================
Update failed.
------------------------------------------
Invalid object name 'AsapRole'.

2/14/2023 1:18:05 PM Executing activity: 00010_RoleName_255
Error occurred while running deployment activity 1.1/00010_RoleName_255
System.Data.SqlClient.SqlException (0x80131904): Invalid object name 'AsapRole'.
   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.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.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
   at System.Data.Common.DbDataAdapter.Fill(DataSet dataSet)
   at Origam.DA.Service.AbstractSqlDataService.ExecuteUpdate(String command, String transactionId)
   at Origam.Workbench.Services.DeploymentService.ExecuteActivity(ServiceCommandUpdateScriptActivity activity)
   at Origam.Workbench.Services.DeploymentService.ExecuteActivity(AbstractUpdateScriptActivity activity)
1 Like
2

I am afraid this could be caused by Deployment Script Dependency Versions Ignored

We might need to do some root deployment scripts cleanup.

3

You must not run Security package alone. If you create new project you have to open your new empty project package. In this case the scripts start from three base packages together in one time and all will be work without problems.

4

This was work on the model root so there was no extra project package. But it works correctly if the scripts are run from the Root Menu package. Then the dependencies are respected.

5

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.