Welcome to the community forums for Theopenem. All responses are provided by other users that wish to help out. Theopenem will not respond to these posts. If you require more assistance than what the community can provide, we offer various paid support options.

Error 87 with UncServices on machine trying to connect to Az Fileshare

Support
Log in to reply
  • D

    Hello,
    im trying to set up the Theopenem but are running into some issues.
    My plan is to have the following setup:

    • One machine on-prem
    • One VM in Azure which is turned off most times and acts as a backup in case the on-prem machine fails (but currently turned on because that’s where the DB is)
    • A shared Azure fileshare, accessed by both machines over SMB / 445
    • Both run on Windows Server 2022

    Connecting the Azure Fileshare works, both machines have it in the overview in Theopenem Web UI and see the remaining storage etc.
    The Com servers cluster is set up as follows:
    88a93711-e7b1-4755-8827-cf109db09e8e-image.png
    All com servers also have a local storage path defined.
    However it seems like the on-prem machine is not able to interact with the azure com server:
    1f969e94-c80b-4d7f-ae8d-512915868535-image.png

    Checking the com server logs for the on prem machine I get the following:

    2024-09-20 14:31:28,231 [24] ERROR Toems_Service.UncServices Error Code: 87
2024-09-23 12:30:27,986 [13] ERROR Toems_Service.EncryptionServices Could Not Decrypt Password. Ensure Your Encryption Key is Correct.
2024-09-23 12:30:28,064 [13] ERROR Toems_Service.UncServices Could Not Connect To Storage Location: \\XXXXXXXXXX.file.core.windows.net

    Ive been researching and trying to change stuff but I cant get behind why this error happens and why It works on the other machine. Maybe I have some error in my understanding / have it configured the wrong way?
    This here is the overview from the on prem machine:
    5ede94c6-1361-457c-a04d-71edacc575b9-image.png

    My first guess was, that 445 is blocked and therefore the on-prem machine cant access the fileshare. However, mounting the fileshare was successfull so i dont think that thats the issue.

    If more information / logs are needed, please let me know.

    Thanks in advance to everybody.

    T 1 Reply 0
  • T

    In admin settings->about are all the version numbers populated?

    D 1 Reply 0
  • D

    @theopenem_admin Everything except the Toec API COM Servers.

    Also only their own version - On Prem:
    bf17d79b-8e07-4058-8752-adbf24132448-image.png

    On the cloud VM its the other way around.

    0
  • T

    Ok, that means it strictly an issue with the API / DB. Did you verify the db encryption key is correct and the same on all servers, the connection strings are all pointing to the correct db, and that the db is allowing remote connections?

    D 1 Reply 0
  • D

    @theopenem_admin Hello, thanks for the quick responses. Unfortunately it doesnt work yet.

    I checked the Web.config of Toems / Toec for the Azure VM and the on prem VM. They all have the same DB encryption key in it, same user login into the DB etc...

    To check if remote connections are even permitted, i started up HeidiSQL on my onprem machine and tried to connect to the DB on the Azure VM with the user & password written in the config files. That also worked.

    Im attaching screenshots of the configs:
    Azure Toems Web Config:
    7c1e09f0-8d6f-4f59-a746-7d259f1c1a6a-image.png

    Azure Toec Web Config:
    42c76620-ddb4-4129-9535-4067c403465c-image.png

    On prem Toems Web Config:
    6b21c21b-c195-4337-9cb8-33c15ba05e32-image.png

    On prem Toec Web config:
    070dd879-4f0e-4085-bd8f-b76dc7d06540-image.png

    Any other idea or place i should take a look at / post information to help troubleshoot?

    0
  • T

    That all seems correct. The only other thing I can think of is that your com server urls are set correctly? Can you reach the azure api from your web browser on the on prem server? Something like:
    http://192.168.56.100:8888/Provision/VerifyDb

    0