Sage Runtime Error 1004 in Excel

If you’re like most people, you use Excel for work and personal purposes. And, since Excel is a powerful tool, it can sometimes malfunction. Unfortunately, when Excel malfunctions, it can be hard to track down the source of the problem. In this blog post, we will discuss how to fix sage runtime error 1004 in Excel. By following our steps, you will be able to troubleshoot and fix any issues with your spreadsheet quickly and easily.

Out of several important features incorporated in the Sage 300 software, the ability to integrate with MS Excel helps businesses and professionals immensely. With this useful feature, you can avoid the manual entry of data from a spreadsheet and thus, can save a considerable amount of time for your business. No wonder why Sage 300 is extremely popular among the business community and professionals all over. 

However, many users of Sage have intimated to us that they have been facing the Sage Runtime error 1004 error message while extracting data in MS Excel. If you are one of them and are wondering how to get rid of this issue, we have it covered for you! In this blog, you will be served with some easy yet highly effective solutions to fix this issue. You just need to execute these steps sequentially.

Here we go!

What Causes the Sage Runtime Error 1004 in Excel?

While there may be several technical issues that may lead to this error, it is mostly caused when the Environment does not have all SEI tables created

Read More : Sage 50 Runtime Error 9

Procedure to Resolve the Sage Runtime Error 1004 in Excel

Here, we will discuss a simple method to fix the Sage Runtime error 1004 in Excel. Please note that this solution will apply only after the first installation, upgrade or immediately after adding a new Environment. It involves the following phases-

Phase 1: Detection of the Issue

• Open SEI via the web interface
• In the Command Center, select the process from which data was being extracted
• Right-click
•  on Design process
• If an error appears saying there is a joint error between an X3 table and an SEI table, the environment needs to be refreshed
  • For example: Error creating join from GACCENTRY.ACCDAT_0 to ZTABCHANGE.DATE_0
• Close the process
• Change Global Environment (bottom of the main SEI window) to the next Environment and test again, as needed.

See Also : Sage 50 Excel Integration

Phase 2: Refreshing the Environment

• Click on the Administration tab
• Choose Manage Env. & D.S.
• Go to the Environments section and specify the environment to be refreshed
• Now go to the Data Sources section and select the X3 data source
• Note down the following values:
  • Database name
  • SEI schema
  • Database schema name (without SEI)
• Now go to the Environments section and click the refresh button for the particular environment
• Go to the Execute Scripts window:
  • X3 Database = note the value for the Database name
  • X3 Schema (Folder) = The part after the period of the value noted above for the Database schema name. 
  • SEI Schema for Custom SQL Objects = note the value for the SEI Schema
  • From the bottom of window, click Run
  • You will get a prompt that will ask if you want to execute all the scripts on this environment by dropping its SQL objects and recreating them. 
  • Checkmark the box “I agree to drop all SQL objects and recreate them.”
  • Click on Yes.

In case you get red circles with slashes, it will mean the script failed to run. Clicking on the circle will give the details of the failure.

Also Read : Sage Payroll Runtime Error 372

Final Words

We hope the steps mentioned above would help you fix the Sage Runtime error 1004 in Excel. In case you are experiencing any difficulties in carrying out the above steps, we would recommend you to take help from some experienced Sage professionals.

Frequently Asked Questions(FAQs)