Skip to main content

NAV 2009 And Earlier - Internal error 52033 in Module 93.

Hi all,

While trying to open a database in Version 4 SP3 (5 SP1) I faced the below error message.

The error message was new to me till today.

Resolution -

The above error also appear of our SQL Start up Parameter 4616.

How to apply SQL Start up Parameter 4616 ?

1. Open SQL Server Configuration Manager.

2. Select MSSQLServer Properties.

3. Navigate to Advanced Tab.

4. Select the Start up Parameter.

5. Navigate to End of the line and add String ;-T4616 as shown below.


Now when you try to login into database, it will not give you an error message.

Regards,
Saurav Dhyani
Labels:
Location: Sector 62, Noida, Uttar Pradesh, India

Comments

Post a Comment

Popular posts from this blog

Microsoft Dynamics NAV 2016 - How to Configure Phone Client.

Hi All, In this article we will discuss how we can connect Microsoft Dynamics NAV 2016 with New Client Launched i.e. Phone Client. This Article Contain Steps for a Android Phone as I have Only Android Phone. I am doing it having all tiers on my windows 8 machine, steps remain same for multiple servers but issues might be different. What we Need (Other what we discuss in this article) -  The Service Tier should be on Public IP . Some of the Data-card does not Provide you Public IP. check it for sure.
28 comments
Read Complete Article »

How to Set Up NavUserPassword Authentication in Business Central.

Hi Readers, In this article we will discuss steps to Setup NAVUserPassword in Business Central on-prem. NavUserPassword is an authentication method that's handled by Business Central Server, but isn't based on Windows users or Active Directory. Each user is set up with a username and password that's configured inside Business Central only. The user is prompted for username/password credentials when they start the client. #msdyn365bc, #credentialtype
1 comment
Read Complete Article »

MSDYN365BC - Data Upgrade To Microsoft Dynamics 365 Business Central on premises.

Hi Readers, We have already talked about the number of steps for upgrading to Business Central on Premises from different NAV versions. After that article, I received multiple requests for an article which list down steps for Data Migration. In this article, we will discuss steps of data migration to MSDYN365BC (on-Prem) from NAV 2017. For this article, I am considering a Cronus Demo Database without any customization. For an actual upgrade project, we will have to complete object merge using compare and Merge process. After the Merge Process, the next step is data migration. Let's discuss those steps. Direct Upgrade to Microsoft Dynamics 365 Business Central (on-Prem) is from following versions - 1. NAV 2015. 2. NAV 2016. 3. NAV 2017. 4. NAV 2018.
21 comments
Read Complete Article »