How to Resolve Sage ACCPAC Error 49153?

thomaslaneApril 7, 2022

260 7 minutes read

Sage programming has been extraordinarily presented for little and medium organizations that can be tweaked by your business prerequisites. It might help you by dealing with CRM, accounts, business-related undertakings, and so forth. Nonetheless, you might go over blunder codes because of various reasons while getting to Sage 300. In the accompanying article, we will talk about one such mistake ‘Sage ACCPAC blunder 49153’ that can hamper the work process of your business.

To get a nitty gritty perspective on blunder 49153, you need to peruse the entire post cautiously and attempt to physically fix the issue.

What is Sage ACCPAC Error 49153?

You might go over the 49153 blunder when you are neglected to login into Sage 300 to test the information base association. It shows that Sage 300 has begun yet can’t interface with the data set. Moreover, you might get the blunder 49153 while highlighting some unacceptable waiter name. Presently, now is the ideal time to investigate the potential causes behind the blunder event and figure out the applicable arrangements.

Find -: Find serial number activation key Sage 50 software

What Causes Sage ACCPAC Error 49153?

Coming up next is a rundown comprise of the multitude of potential causes that might prompt Sage ACCPAC blunder 49153.

In view of an invalid ODBC DSN, you might encounter blunder 49153.
Whenever the information base is disconnected, a mistake could show up.
In the event that the Sage 300 ERP programming is hindered by the Windows firewall, blunder 49153 may occur.
The DNS is fixing the server name to the wrong IP address.

How to Fix Sage ACCPAC Error 49153?

Given beneath are the finished strides to fix ACCPAC blunder 49153. On the off chance that, you face any troubles while settling the blunder, immediately reach out to our group.

First and foremost, send off a Sage data set arrangement, then click on the Company and System Database Profiles.
Presently, you really want to confirm the Data Source or Server name, Database Name, and Login ID.
From that point forward, pick Control Panel and snap on Administrative Tools.
Pick the Data Sources, then send off the 32-digit variant of ODBC Data Source Administrator.
Then, access way C:\Windows\SysWOW64\odbcad32.exe on 64-digit PCs.
Search for the Data Source name and enter the administrator certifications in the SQL Authentication.
Guarantee that every one of the leftover settings have been set as default.
Finally, really take a look at the information base network from the DSN and reinstall the SQL Native Client Driver.

How to Fix Sage Error Code 49153?

To determine this blunder, you can carry out various arrangements. For example, you can check the data set association, check this product on different frameworks, utilize the order line to actually look at the data set server, inspect the SQL server, really look at ODBC settings or open the library to refresh the server way.

Presently, we will see this large number of various ways with a bit by bit guide.

Fix 1: Check Your Database Connection

Prior to carrying out any specialized practice, one ought to send off the Sage 300 application to really look at the information base association. You can analyze assuming there is a specific information base that is causing issues or every one of the data sets making blunders.

To do as such, you want to go to the Sage 3000 DBSETUP utility that keeps all the data set associations data connected with your Sage 300 organization. Whenever you are signed into your record, seek after the means expressed beneath:

Hit the “Begin” button.
Click on the “All Programs” choice.
Presently, change to the “Sage”.
Pick “Sage 300 2016” It can show different names. Contingent upon your form, you can pick the name.
Click on the “Information base Setup”.
Login to the record utilizing your right ID and secret key.
Hit the “Alright” button.

Whenever you are finished playing out these means, you will see the arrangement profiles accessible in the Sage 300 application. Now, you can click two times on any of the arrangement profiles with the goal that you can see the properties.

This is the means by which you can really look at the server alongside the name and the information base. This assists you with treating the mistake in like manner.

On the off chance that you are getting the blunder because of the various data sets then you ought to address the utility settings. The issue can happen because of the unfortunate PC association or SQL server. In this way, you can really take a look at them to determine the blunder 49153 Sage (Accpac).

Fix 2: Ask If the Error is Received by Other Users

In this strategy, you are expected to request different clients from Sage 300 on the off chance that they are getting a similar mistake. Assuming different clients experience this blunder, it shows that the issue is really with your information base server.

On the other hand, you can send off Sage 300 programming on another PC. Sometimes, your product doesn’t answer as needs be because of the framework or equipment issues. Assuming your product chips away at another PC, it implies there is an issue with your gadget.

To fix this issue, you can look at the accompanying ways of affirming assuming your information base is running.

Fix 3: Check Your Database Server utilizing Command Prompt

To check the information base server, you can visit the server console and confirm the server status. Here, you can ping the information base server by its name. This is a simple method for seeing whether the information base is running or the name is apparent on another framework. This is the way to find out:

Click on the “Begin” button.
Type “Order Prompt” in the inquiry bar.
Hit the “Enter” key.
At the point when you see the “Order Prompt” window, begin composing “ping databaseservername”.
Then, at that point, press the “Enter” key.

On the off chance that a spring up seems saying “Ping solicitation couldn’t find have sql2016. Kindly check the name and attempt once more” then, at that point, this blunder is brought about by its server.

Presently, you can check the information base condition and afterward restart your framework. Once done, you can actually take a look at the data set server. On the off chance that you neglect to ping it by name, attempt to ping it by the IP address.

Fix 4: Check SQL Server

Here, we will execute the order to actually take a look at the SQL Server. For that, you can follow the means taught underneath:

Click on the “Begin” button.
Type “services.msc” in the inquiry bar.
Hit the “Enter” key.
Presently, really take a look at the SQL Server (SQL Express). On the off chance that the status doesn’t begin, you can click right on the “Name” and hit the “begin” button.
Since you have begun the SQL server, you can take a stab at signing in to your Sage 300 application. Assuming you again neglected to login, go with different strategies.

Fix Open the Registry

On the off chance that you are confronting information base blunder issues, you can change the way of your server. This should be possible by utilizing the library. The following are the accompanying advances that can be followed:

Press the “Windows” + “R” keys to send off the “Run” box.
Type “Regedit” in the inquiry bar.
Press the “Enter” key.
See as the “HKEY_LOCAL_MACHINE-SOFTWARE\wow6432Node\ACCPAC International, Inc. \ACCPAC\”.
Here, you really want to refresh or change the server way in the Sage300 organizer which should be put in the Shared Data and Programs.
Open your “SQL Server 2014 Configuration Manager” and extend the SQL Native Client Configuration” area.
Then, at that point, click on the “Client Protocols” to analyze the Shared memory, Named Pipes, TCP/IP, on the off chance that they are empowered or not.
Presently, go to the “SQL Server Service” and begin the administrations once more.
When you change the settings for the SQL server, the odds are feasible to fix the issue. From that point, you can attempt to sign into the server.

Fix 6: Open ODBC Settings

On the off chance that no strategy works, changing the ODBC settings can work. In this strategy, we will initially check the ODBC settings and afterward test data set availability from the Control Panel.

Fix 6.1: Check ODBC Settings

Press the “Windows” + “R” keys to send off the “Run” box.
Type “%WinDir%\system64\odbcad64.exe” in the pursuit bar.
Press the “Enter” key.
Click on the server name in the “ODBC Data Source Administrator” window. This will show you the data.

Fix 6.2: Fix the Issue

Open the “Savvy Database Setup” and the “Framework Database Profiles”.
Check which Login ID, Server name, Database names, Data Source are set.
Presently, open the “Control Panel”.
Click on the “Managerial Tools”.
Go to the “Information Sources (ODBC)”.
Open the “ODBC Data Source Administrator” (32-digit adaptation).
Then again, you can follow the way for 64-bit: C:\Windows\SysWOW64\odbcad32.exe.
View as the “Information Source” or “Server” name.
In the “SQL Authentication”, enter the ID and secret key.
Ensure that the settings stay as default.
Test your information base network utilizing the DSN.

This is the way you can actually look at the ODBC settings and data set availability. You can likewise attempt to reinstall the SQL Native Client driver. This will assist you with fixing the issue without a doubt.

Find Also-: Sagepay error 5080 form transaction registration failed

Twisting Up!

As we have seen, Sage ACCPAC mistake 49153 is very little interesting to determine. Now and then, this mistake might get settled just by really looking at the information base association or SQL server. Assuming you are as yet getting a similar issue even in the wake of applying every one of the potential arrangements, then go ahead and get in touch with us. We will help you in settling the issues connected with Sage so you can keep chipping away at the organization record. In the event that you feel reluctant to converse with our specialists, compose a discussion to us and post it on our site.