Following on from an earlier post about Sage 300 Subscription Expiration messages, we have subsequently received a number of questions related to what the effect of read-only mode entails. As we have been unable to obtain anything documented in this regard, we did some internal testing in support and will be posting our findings for each module. Herewith our findings for the Administrative Services Module.
In Sage 300 Malaysia E-Invoicing, posted transaction in Account Receivable, Account Payable and Order Entry will be available in EI Outgoing processing screen for submission purpose.
*If client does not have Order Entry module , Account Receivable module will be used instead.
According to Inland Revenue Board Malaysia requirement on E-Invoicing, there is a series of guidelines and requirement that we need to comply. We…
in Sage 300 Web Screens
The message, “Please correct the following issue(s): Undefined”, may appear when signing into Sage 300.
In many cases this is caused by a DNS name resolution issue. Also, for installations that use SSL certificates (HTTPS) the error may be attributed to improper application of the certificate on the server.
Steps to resolution:
First verify if the same error occurs on the server…
Part 1 : How to setup Chinese language User Interface:
1. Ensure you have install the Chinese language packs via the Sage 300 installer.
2. System locale and Region settings.
3. Login as the Users which language is set as Chinese in the Users setup.
Part 2 : How to capture data with Chinese Character:
1. Database collation has to support Chinese characters , you may use Chinese_PRC_CI_AS
This collation support multiple…
Sage 300 Malaysia E-Invoicing (EI), and Singapore Invoice Now (VV) module is a 4 corner model that Sage 300 EI/VV module is the Corner 1, and Corner 2 is Peppol access point provider.
Which mean Sage 300 need to be able to establish connection with Corner 2 to perform E-Invoicing seamlessly via PEPPOL network.
Often user encounter Network Connection error as below.
Screenshot of error message:
Assuming the environment…
Following on from an earlier post about Sage 300 Subscription Expiration messages, we have subsequently received a number of questions related to what the effect of read-only mode entails. As we have been unable to obtain anything documented in this regard, we did some internal testing in support and will be posting our findings for each module. Herewith our findings for the Accounts Receivable Module.
TPAC South Africa 2025 (Feb 20-22) brought together Sage 300 partners, ISVs, and industry leaders to explore the latest innovations and opportunities in the Sage ecosystem. It was great to join Richard Jang in the keynote and have John Thomas join us virtually for one of the sessions. One theme from the event was the power of Sage CRM when integrated with Sage 300—and the massive revenue potential this unlocks for partners…
Following on from an earlier post about Sage 300 Subscription Expiration messages, we have subsequently received a number of questions related to what the effect of read-only mode entails. As we have been unable to obtain anything documented in this regard, we did some internal testing in support and will be posting our findings for the various modules.
Herewith our findings when testing functionality in the the Accounts…
We recently had a case where a customer complained that their subscription licenses expired, resulting in their system going into read-only mode during a rather busy period prior to year-end however they received no warning messages prior to the system becoming read-only.
This prompted an investigation during which we confirmed what is supposed happen, as well as tested that this does indeed occur, and I thought to share…
We recently had a case where a customer got the below error whenever they tried printing any reports. 
Often when cases are first logged with support, not all the relevant detail is supplied and, as a result, the complete picture often only becomes clear after several interactions. So, to make this easier to read, I have summarised all the information gathered in the next paragraph.
In this specific instance, the issue…
We recently were requested on some clarification on how LanPaks are consummed for Sage 300 integrations with 3rd parties.
Where the 3rd party was advising the client that Sage had changed our Lanpak policies so therefore the integration would no longer work with the lanpak count that they originally had. This occurred after they upgraded the environment from Sage 300 2019 to 2024.
They believed that they could no longer…
We have updated our licensing version for Sage 300 Subscription customers. In the License Manager you will now see Version 8.8 for most modules and 8.0 or 7.3 for Payroll. In March 2024, Payroll will be exclusively 8.0. This simplifies your upgrade process by not having to update your Subscription licenses for every new release.
You can find out what version of Sage 300 you are using from the Help menu. Choose About…
A customer recently encountered the error “Cannot connect to Sage 300 Signon Manager” and, when checking the event viewer, the error code 2147943660 was displayed.
To get the relevant error message description, firstly convert the error code 2147943660 to hex: 800704EC.
This can be done using e.g. Google or Windows calculator in Programmer mode.
Next, take the last 4 digits (04EC) and convert to decimal…
Employers in different Provinces in Canada and different States in the US have their own offerings when it comes to vacation time but all offerings are within the regulations in each employee’s jurisdiction. A couple of commonly used methods with setup steps based on certain scenarios are referenced below:
A wildly unused feature of Sage 300 is General Ledger Integration. This feature will increase the level of details that populate GL entries from the subledgers.
How to:
GL Integration is specific to each modules.
The most common error in web screens appears during login.
This error is an Unexpected error:
An unexpected problem has occurred. Please try again or contact your administrator for assistance.
What to look for:
Financial reporter derives values from specification defined in Column A and B in the spreadsheet.
The most common use is to define an account group to a section in the sheet. When troubleshooting issues with FR the first level is to verify accounts associated with groups.
How to verify accounts to groups:
After diagnosing issue with SQL Profiler, determine a long query against PMPROJS table and then single record fetches to PMPROJT table.
The behavour is intermittent as not all AP Batches are Project Job Cost entries so only occurs when particular projects are referenced in AP entry.
Sage 300 PJC was not optimized to work with large open project data set, and does not filter by a particular project or phase, but queries…
With the release of Sage 300 2023 there is a major change to Sage 300 Database structure. Download now includes 4 document files:
1. Sage 300E What's New in Version 2023.3 (Video)
2. Sage 300 2023 Release notes
3. Sage 300 Enhanced Security (Has step by step information on how to setup)
4. Sage 300 Security guidelines.
With the recently released Sage 300 2023 Product Update 3, the following message may occur if your user account password has expired when attempting to log in to Sage..
"You password has expired. Ask your administrator to change it".
In the lead up to this expiry, you would receive a message "Your password will expire in XX days. Do you want to change it now?"..
It is recommended to change the password…
After installing 2023 Product Update 3 (2023.3) you may encounter the following error message during the initial configuration of the Database ID Vault and Store Databases.
The assumption is that the Vault and Store Databases have been created in SQL Server Management Studio and the correct SQL Login ID and Password has been entered.
Possible reasons for this error could be:
There was a scenario that the client didn't uninstall Sage Intelligence workstation setup before their old server was already offline with the new server in place. When the client tried to uninstall Sage Intelligence workstation setup, the program was looking for the old server which is already offline with "Cannot connect network server" error during the uninstall.
Please make a backup of the registry if…
In Sage 300, it allows you to import one or more entries into P/O Purchase Order by using an import template to import the data. There are different types of files formats you can generate to fit your needs. For example, Excel, Single CSV file, CSV file, Access, ODBC, and XML.
The steps to generate the import template are as follows:
This is a known issue with task scheduler and is being investigated by Sage Intelligence development.
As a workaround, use a batch file to launch report and add in a task kill statement to clean process.
For example.
TASKKILL /F /FI "USERNAME eq <UserName>" /IM Excel.exe
(Note: Change <UserName> to Domain\User or Local user that has rights to execute in the operating system).
The following error message may occur when running a Sage 300 Intelligence Report :
[Microsoft][ODBC SQL Server Driver][SQL Server]Login failed for user 'sa'.
Viewing the Tenant Cache you can see that the DB Pswd field is blank:
To resolve this message, you will need a Connector Module entitlement.
Launch the Sage Intelligence Connector
Select the Sage Accpac (Auto Connect) connection.
Uncheck the "Use Auto…
