Ir al contenido principal

Sage X3 - Regenerate Syracuse Certificate



Origen fuente: http://sagex3asia.blogspot.com/2017/04/sage-x3-regenerate-syracuse-certificate.html
Autor: https://www.blogger.com/profile/15857213250701606716
There are some of the reasons that you need to regenerate Sage X3 Syracuse certificate, the reasons could be:
1. Expired of certificate
2. Uninstall or re-install of X3 Syracuse
3. Changes of server information
4. Incomplete, corrupted or missing of information in Certificate
5. Changes of password of SageRT (Granted administrator user running X3 services)

The possible error below that you encountered below might required regenerate the certificate in order for you able to login Sage X3 again.

1. Cannot read passphrase file. Maybe it has been created under another operating user.

2. Error connect ECONNREFUSED.



Here are the steps to regenerate certificate for Syracuse:

1. Go to Syracuse installation directory, <Syracuse>\syracuse\cert_tools. Make backup of output folder by rename it.Click on certgen.bat, this will open a command prompt.


2. Fill in all necessary information for Country, State, City, Organization, Organization Unit, Name and Validity Days. Enter and confirm the passphrase. 


3. ca.cart file will be generated in output folder.


4. In the same command prompt, press 1 to start new key generation.


5. Enter Server name, Server name for TCP Connection and Validity days. Enter and confirm passphrase created as step 2. Enter X3 port number, 8124. Click enter to certificate, public and private key.


6. Exit command prompt, new files have been created in output folder.


7. Copy .cart, .crt and .key files into <Syracuse>\syracuse\<servername> folder.


8. Copy .pem file into ..\runtime\keys folder.


9. To complete the certificate generation, logout and re-login windows with SageRT user. Open command prompt as Administrator, navigate to <Syracuse>\syracuse folder in command prompt. Enter passphrase.cmd with password and enter to rewrite and re-upload the certificate to X3 server.


10. Certificate regeneration complete. 


11. Restart Syracuse and you may login Sage X3 now.







Entradas populares de este blog

Valores de fstat

Fstat fstat  is a numeric status that is returned upon execution of a database operation, a sequential file operation, or a lock instruction. Syntax fstat Examples # MYTABLE is a table with a key called KEY1, that has a unique component called KEYVAL # Create a record in the table MYTABLE with they key value 1 if it doesn't exist Local File MYTABLE [MYT] Read [MYT]KEY1=1 If fstat [MYT]KEYVAL=1 : Write [MYT] If fstat MSG="The key was created in the mean time" Else MSG="Key created" Endif Else MSG="Key already exists" Endif Details fstat  is always set to '0' if the operation is successfully completed, and has a non-null value if there is an error: In a sequential read ( Getseq  and  Rdseq ),  fstat  is set to '1' at the end of the file. On  Lock ,  fstat  is set to '1' if the lock could not be performed. For a database operation ( Read ,  Look ,  Readlock ,  For ,  Write ,  ...
Leer más

SAGE X3 SILENT IMPORT (IMPORTSIL) WITH ERROR CATCHING

FUENTE ORIGINAL: https://pluginx3.com/en/blog/post/sage-x3-silent-import-importsil-with-error-catching.html You already know how to manually generate a CSV file in order to import it threw a template in Sage X3. But If you wonder how to catch detailed errors after a silent import here is the solution. Sometimes you need to catch the incoming errors in order to alert the end-user regarding an issue. Closed period, wrong date etc …. Unfortunalty the standard Sage X3 silent import function doesn’t natively show the detailed errors during the import process. Call IMPORTSIL([M:IMP2]MODIMP,[M:IMP2]NOMIMP) From GIMPOBJ And the standard function ERR_IMPORT will only show the overall status of the importation and not the detailed errors. IMPORTSIL function is pushing all the log data into a tracefile in order to avoid any popup on end-user screen. So you have a log file available in order to search for errors in it. Sage X3 runtime is using the same principals standards as any shell for log...
Leer más

3 ways to send a mail from code in Sage X3, with more attachments too

Origen Fuente:  https://en.sagedev.it/sagex3/send-mail-from-code-with-attachments-sage-x3/ Autor:  https://en.sagedev.it/category/sagex3/ In this post I’ll show you how to send a mail from adonix code in Sage X3. The points we will face are: 1) Meladx/Send introduction 2) Sending  through  meladx (the best way for me: at the end with just a single code line you send a mail!) 3) Sending  through  Workflow 4) Sending  through  ENVOI_MAIL(…) From AWRKMEL Sending mail from code in Sage X3: Send vs meladx Sage X3 has two native ways for sending mails. The first way is  meladx  executable file, that you can find in  runtime\bin  directory. The seconde one is Send instruction, that was used to send mail through an application of the client station (for more information on “Send GSERMES”  go here ). The Meladx executable Meladx send messages through SMTP/POP3 protocols by means of the mail  ...
Leer más