Sage X3 Africa and Middle East

Most likely you are running on patch level less than 8 if on v1. It is recommended to patch up to a higher patch on any version. Please contact support for a fix.

SMTP server is specified in general parameters and it uses default port 25 Setup > Usage > General parameters Access Supervisor module and update workflow parameters

This could be due to various reason, these include the following -an incorrect smtp server is specified in parameters -specified smtp server requires authentication -specified smtp server requires ssl/tls activation For the last two option,…

Access your workflow in function Setup > Usage > Workflows (GESAWA) Enable the debug mode Save and validate your workflow Test the workflow, a log file will be displayed

Can someone please advise on how to fix the error below. it appears every time I try to print reports (Custom and Standard). error | Job 4 - ERR 262 from the publishing server: The connection to the file server has failed.

X3 workflows does support SSL/TLS security mechanisms by default. As a work-around, a relay server can be configured as middleware to accept unencrypted messages from sage x3 and the relay server will forward emails to the external smtp server as per…

Means value provided is not a string, you can enclose arguements in quotations eg "BUG" instead of just BUG.

Review credentials setup in services Review antivirus setup. Start by stopping/disabling antivirus, if Syracuse starts then you will need to whitelist Syracuse in the anti-virus settings

Ensure you are running on latest patch sets of Syracuse Review log files if there is extra logging of information

Check for antivirus and review if it is blocking Stop Syracuse connections before initiating updates

Memory leaks can show as one Syracuse process utilising more memory and mongodb crushing. Prevalent in Syracuse releases below SyracuseServer 12.5 SyracuseServer 11.19 SyracuseServer 9.19 Update Syracuse to higher patches paying attention to…

NB. Standard functionality does not allow Fixed Assets to be updated through an import template.

Hi All Can someone please assist me with this error. The error displays when i try to run the stock accounting interface for all sites.

My client wants the expense to be created upon receipt of the asset. Standard Sage X3 creates Expense only when an invoice gets captured whereafter the user can capitalize the expense to create an asset. We are contemplating special development for…

I posted two supplier Invoices and observed it does not create a journal. I checked the accounting task and the journal on hold shows two. I check recurring tasks for the active time and it's okay. I deactivated the accounting task. Restarted batch server…

Hello Everyone, we tried to update X3 to the final version 12.0.23. but just the X3 folder was updated and the other folder was not updated. and now we get errors like this: and most of these source files are not in the TRT folder ??

Fix. Navigate to Administration > Administration > Servers > Hosts Select the host from the list and click Edit Enter a positive value in the Number of Web service child processes box Save and Test

Cause : The XML or JSON file is too big. Fix: Remove all defaulted and unnecessary fields from the XML/JSON stream and test.

adxwss.optreturn option allows for specification of return format. for JSON format <requestConfig xsi:type="xsd:string"> adxwss.optreturn=JSON </requestConfig> For XML return <requestConfig xsi:type="xsd:string"> adxwss.optreturn=XML…

include the highlighted option in the web service call <requestConfig xsi:type="xsd:string"> adxwss.beautify=true </requestConfig>

1. Login into the system 2. Navigate to Administration > Administration > Web Services > Classic soap pools configuration 3. Configure your web pools

Increase the timeout settings by a factor . 1. Navigate to Administration > Administration > Hosts 2. Click edit on you server 3. Increase the Return Request Timeout 4. Test The timeout is in seconds, this value should be increased cautiously…

Sometimes you might need to terminate a process in sql server. 1. Open Sql server management studio 2. Open a new query 3. execute command below, processID is the sql process number kill processID NB. Ensure you terminate a correct process…

Fix. Review sql permissions on roles such as X3_ADX_SYS, compare with a working system. Consult a database administrator for assistance.

Cause : Disk space could be running out. Fix. Review disk space, investigate SQL server health status.