Upgrade customized CAL BCv14 to BCv19 error on Sync NAVApp empty table migration extension with The input parameter OldName is not allowed to be null

(5) Share

Report

Posted on by Jerome Cader

Trying an upgrade from BC Cronus v14 CU18 with a 2 custom tables to BC v19.4 on premise,

using the following guide docs.microsoft.com/.../upgrade-to-microsoft-base-app-v19

On Task 14: Task 14: Synchronize final extensions

Sync-NAVApp -ServerInstance BC19CronusAllObj -Name "bc14baseapptablesonly" -Version 1.1.0.0

gives the error

Sync-NAVApp : Changes to the tenant database could not be applied. Affected tables will not be available.
The first error was:
Cannot delete the O365 Device Setup Instructions table from the Demo Test5 Database NAV (14-0) database because it contains data
for the company.
Retry the operation when the problem has been resolved.

when trying to force the sync

Sync-NAVApp -ServerInstance BC19CronusAllObj -Name "bc14baseapptablesonly" -Version 1.1.0.0 -Mode ForceSync -Force

gets the error :

Sync-NAVApp : The following SQL error occurred after the SQL command was canceled:
Either the parameter @objname is ambiguous or the claimed @objtype (OBJECT) is wrong.
Error: The input parameter 'OldName' is not allowed to be null.

I have the same question (0)

All responses (10)

Answers (1)

CU30101423-0 2 on at

Like (1)

Report
Copy link

Link copied!

@Sumit Singh

What changes need to be made to the app.json file?

Was this reply helpful? Yes No
Suggested answer

Sumit Singh 10,865 on at

Like (3)

Report
Copy link

Link copied!

Hi @CU30101423-0,

We already having a verified answer which might work i.e. updating app.json.

please try this.

Was this reply helpful? Yes No
Suggested answer

OussamaSabbouh 7,840 on at

Like (2)

Report
Copy link

Link copied!

Hello,

The error happens because the O365 Device Setup Instructions table still has data, BC can’t delete it during Task 14.

Fix:

Delete all data from that table.

Restart the BC19 server.

Re-run syncs in order:

System App → Base App → Application → other extensions → your migration app.

Only use ForceSync if Microsoft explicitly says so.

Regards,
Oussama Sabbouh

1 people found this reply helpful.

Was this reply helpful? Yes No
CU30101423-0 2 on at

Like (2)

Report
Copy link

Link copied!

I have the same problem. Did anyone solve it then?

1 people found this reply helpful.

Was this reply helpful? Yes No
Thanigaivelan S 22 on at

Like (2)

Report
Copy link

Link copied!

Hi Creppz,

Did this solve your issue ? What should be updated in the app.json ?

Thanks.

Was this reply helpful? Yes No
Creppz 5 on at

Like (2)

Report
Copy link

Link copied!

Hi Jerome,

Which property did you need to update in the app.json ?

Thanks.

Was this reply helpful? Yes No
Verified answer

Jerome Cader 62 on at

Like (2)

Report
Copy link

Link copied!

Issue resolved after updating the app.json for the upgrade extension.

Was this reply helpful? Yes No
Suggested answer

Marco Mels on at

Like (1)

Report
Copy link

Link copied!

Hello,

Best probably is to raise this issue to Microsoft.

Thank you.

Was this reply helpful? Yes No
Jerome Cader 62 on at

Like (2)

Report
Copy link

Link copied!

Statement: exec sp_rename N'"dbo"."Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13"', N'Printer Selection$437dbf0e-84ff-417a-965d-ed2bb9650972', N'OBJECT'; IF (SELECT OBJECTPROPERTY(OBJECT_ID(N'dbo."Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$Key1"'), N'IsPrimaryKey'))=1

EXEC sp_rename N'dbo."Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$Key1"', N'Printer Selection$437dbf0e-84ff-417a-965d-ed2bb9650972$Key1', N'OBJECT';

ELSE BEGIN

DECLARE @KeyName sysname = (SELECT [name] from sys.indexes idx where idx.is_primary_key = 1 and idx.object_id = object_ID(N'Printer Selection$437dbf0e-84ff-417a-965d-ed2bb9650972'));

exec sp_rename @KeyName, N'Printer Selection$437dbf0e-84ff-417a-965d-ed2bb9650972$Key1', 'OBJECT';

END; IF OBJECT_ID(N'dbo.Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemId', 'UQ') IS NOT NULL BEGIN exec sp_rename N'"dbo"."Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemId"', N'Printer Selection$437dbf0e-84ff-417a-965d-ed2bb9650972$$systemId', N'OBJECT' END

IF OBJECT_ID(N'dbo.MDF$Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemId', 'D') IS NOT NULL BEGIN exec sp_rename N'"dbo"."MDF$Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemId"', N'MDF$Printer Selection$437dbf0e-84ff-417a-965d-ed2bb9650972$$systemId', N'OBJECT' END

IF OBJECT_ID(N'dbo.MDF$Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemCreatedAt', 'D') IS NOT NULL BEGIN exec sp_rename N'"dbo"."MDF$Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemCreatedAt"', N'MDF$Printer Selection$437dbf0e-84ff-417a-965d-ed2bb9650972$$systemCreatedAt', N'OBJECT' END

IF OBJECT_ID(N'dbo.MDF$Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemCreatedBy', 'D') IS NOT NULL BEGIN exec sp_rename N'"dbo"."MDF$Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemCreatedBy"', N'MDF$Printer Selection$437dbf0e-84ff-417a-965d-ed2bb9650972$$systemCreatedBy', N'OBJECT' END

IF OBJECT_ID(N'dbo.MDF$Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemModifiedAt', 'D') IS NOT NULL BEGIN exec sp_rename N'"dbo"."MDF$Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemModifiedAt"', N'MDF$Printer Selection$437dbf0e-84ff-417a-965d-ed2bb9650972$$systemModifiedAt', N'OBJECT' END

IF OBJECT_ID(N'dbo.MDF$Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemModifiedBy', 'D') IS NOT NULL BEGIN exec sp_rename N'"dbo"."MDF$Printer Selection$4bde5a55-7fec-4105-b8c8-d2c531b07c13$$systemModifiedBy"', N'MDF$Printer Selection$437dbf0e-84ff-417a-965d-ed2bb9650972$$systemModifiedBy', N'OBJECT' END

Was this reply helpful? Yes No
Jerome Cader 62 on at

Like (2)

Report
Copy link

Link copied!

Message App Sync Exception -- Microsoft.Dynamics.Nav.Types.Exceptions.NavSqlException: The following SQL error occurred after the SQL command was canceled:

Either the parameter @objname is ambiguous or the claimed @objtype (OBJECT) is wrong.

Error: The input parameter 'OldName' is not allowed to be null.

---> System.Data.SqlClient.SqlException: Either the parameter @objname is ambiguous or the claimed @objtype (OBJECT) is wrong.

Error: The input parameter 'OldName' is not allowed to be null.

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)

Was this reply helpful? Yes No