One of our Application consultants ran into the error below while renaming a company in NAV 2013. Shortly thereafter, another developer ran into the exact same error while renaming a field in a table. What’s going on here? This was never an issue with previous NAV versions.
The fix ended up being rather simple: Re-open the database either by picking it from your list of available databases or type in the case exactly as it appears in the dropdown list of databases. That’s it.
Here is the error in question:
The following SQL Server error or errors occurred when accessing the Customer table: 15333,”42000″,[Microsoft][SQL Server Native Client 10.0][SQL Server]Error: The qualified @oldname references a database (demo Database NAV (7-0)) other than the current database.
SQL:
{CALL [sp_rename](?, ?, ?)}
The problem lies in the incorrect case of the database name that was opened in the Development Environment. Opened as “demo Database NAV (7-0)”, the error disappears when opened up with the name being in the identical case as the database name in the list: “Demo Database NAV (7-0)”.
Update: This is now fixed with MBS hotfix build NAV 2013 35117. KB ID 350382.
