Posts made by Cycy

@amaury In this case, download and test before uploading to the server.

@amaury Let TheOpenEM download the msi file.

@amaury Does running this command msiexec.exe /i "C:\Program Files\Toec\AppData\95d39e86-2601-48b0-9a9f-75e12d5a5570\MicrosoftEdgeEnterpriseX64.msi" manually work?

@amaury see: https://help.pdq.com/hc/en-us/articles/220530887-MSI-Cannot-Open-File-Error-1620

Hi
The Toec client must be installed.
It uses the system account
Otherwise look at the log file in C:\Program Files\Toec\logs\service.log

@chavi Thank you Chavi for your reply.
I successfully installed my config on my new server.
The problem was the mysql export.

@chavi and @theopenem_admin I forgot to specify when importing on the new server, I got the error set --binary-mode to 1 and to solve the problem I saved the sql file in utf8.
Maybe that's the problem - any ideas?

@theopenem_admin
I recovered the dbencryption key from the old server.
And for the database dump I used the following parameters:
--events --routines --triggers
And I also retrieved the ComServerUniqueId of the old server.

@chavi and @theopenem_admin Hi,
If I export from the Web UI of the new server.
It generates a bad certificate.
So I imported the certificates from the old server.
Certificate.txt

@theopenem_admin Yes, I have exported the certificates from my old server.
And I installed them on the new server which has the same name and ip address.

@theopenem_admin Thank you for your reply.
I have followed the steps but in ClientApi.log I have the following error:
2024-07-01 15:49:21,490 [9] ERROR Toems_Service.Entity.ServiceCertificate Could Not Validate Certificate: CN=24cd4c16-8bab-4e21-9ff7-dda7531a4df7, O=Casa Corp
2024-07-01 15:49:21,490 [9] ERROR Toems_Service.Entity.ServiceCertificate Could not find the required object.

@chavi and @theopenem_admin Hi
I would like to try this procedure to change to a newer server.
But without having to reinstall the client on the workstations.
Many of my workstations are outside the network.
Maybe an idea
Thanks

@theopenem_admin Thanks, that would be great.

@theopenem_admin Too bad I'll have to change my machine.
This is the machine where I installed the very first version of TheOpenEM 1.1.
Now I have to figure out how to migrate from one machine to another.
Thanks again for your answers.

@theopenem_admin Yes, my VM is on hard disks.
For the moment, extraction is at letter R.
Once the extraction is complete, is it possible to launch the import manually?

@theopenem_admin
Yes, there is data.
But I think my VM is slow to extract files.

 Répertoire de C:\Program Files\Theopenem\Toems-API\private\winget_manifests\winget-pkgs-master\manifests

29/01/2024  14:54    <DIR>          .
29/01/2024  14:54    <DIR>          ..
29/01/2024  13:51    <DIR>          0
29/01/2024  13:51    <DIR>          1
29/01/2024  13:51    <DIR>          2
29/01/2024  13:52    <DIR>          3
29/01/2024  13:52    <DIR>          4
29/01/2024  13:52    <DIR>          5
29/01/2024  13:52    <DIR>          6
29/01/2024  13:52    <DIR>          7
29/01/2024  13:52    <DIR>          8
29/01/2024  13:59    <DIR>          a
29/01/2024  14:07    <DIR>          b
29/01/2024  14:13    <DIR>          c
29/01/2024  14:13    <DIR>          d
29/01/2024  14:18    <DIR>          e
29/01/2024  14:21    <DIR>          f
29/01/2024  14:23    <DIR>          g
29/01/2024  14:27    <DIR>          h
29/01/2024  14:29    <DIR>          i
29/01/2024  14:31    <DIR>          j
29/01/2024  14:37    <DIR>          k
29/01/2024  14:39    <DIR>          l
29/01/2024  14:42    <DIR>          m
29/01/2024  14:54    <DIR>          n
               0 fichier(s)                0 octets

The extraction is still not finished.

Hi,
I have activated the Winget function.
But when I run the winget update import, I get the following error:

2024-01-29 13:50:03,771 [Worker #12] INFO  Toems_Service.Workflows.WinGetManifestImporter Starting Winget Manifest Import Process
2024-01-29 13:50:03,817 [Worker #12] INFO  Toems_Service.Workflows.WinGetManifestImporter Downloading Updated Manifests
2024-01-29 13:50:43,645 [Worker #12] INFO  Toems_Service.Workflows.WinGetManifestImporter Extracting Manifests
2024-01-29 14:20:05,835 [Worker #11] INFO  Toems_Service.Workflows.WinGetManifestImporter Starting Winget Manifest Import Process
2024-01-29 14:20:05,851 [Worker #11] INFO  Toems_Service.Workflows.WinGetManifestImporter Downloading Updated Manifests
2024-01-29 14:20:07,397 [Worker #11] INFO  Toems_Service.Workflows.WinGetManifestImporter Could not download manifests
2024-01-29 14:20:07,770 [Worker #11] ERROR Toems_Service.Workflows.WinGetManifestImporter System.Net.WebException: Une exception s'est produite lors d'une requ.te WebClient. ---> System.IO.IOException: Le processus ne peut pas acc.der au fichier 'C:\Program Files\Theopenem\Toems-API\private\winget_manifests\master.zip', car il est en cours d'utilisation par un autre processus.
   . System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   . System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   . System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
   . System.Net.WebClient.DownloadFile(Uri address, String fileName)
   --- Fin de la trace de la pile d'exception interne ---
   . System.Net.WebClient.DownloadFile(Uri address, String fileName)
   . Toems_Service.Workflows.WinGetManifestImporter.DownloadManifests()

No import completed successfully.
Thanks for your help

@daodio2 Hi,
Can you give me a recap
I can't understand your problem.

@daodio2 Hi
You need to approve your server/workstation.
In Computers / Approval Requests

You need to use a script module:
https://docs.theopenem.com/ui/modules/script/script.html