This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Upgrade error when updating to Enterprise console 4 on a air gapped network

Hello,

I'm trying to upgrade my enterprise console 3.0 to 4.0 en finally to 4.5. The upgrade of the console succeeded but i receive an error when i want to configure the update manager. The error is: "couldn't create cataloque sdds.local".

The enterprise console is on an air gapped network. I copy the complete library folder from an server connected to the internet to my air gapped server. The sophos service account has full control on the folder where i copy the library.

I have a seperate SQL server which is succesfully upgraded to 4.0.

The server which is connected to the internet is not yet upgraded to 4.0. Can this be the problem? Can i still use the update's on my old (3.0) configuration when i upgrade this server to 4.0?

Are there any idea's what the problem could be when is not the update folder?

Witht best regards,

Peter

:10299


This thread was automatically locked due to age.
Parents
  • Hello Peter,

    I didn't ask about the "parent" configuration of your air gapped server (AGS). I assumed you were using something like \\AGS\updates and let EM Library pull the stuff from there. I might misunderstand you but it sounds like you were (and are) writing directly to the share(s). When I tested air gapped updating I had configured the AGS to "loop back" to shares created on the removable medium - I've never copied to the "target" shares.

    There's a description for Failed to acquire product information. The article lists common problems and how to resolve them. It might help you to find out what's still missing.

    Christian 

    :10389
Reply
  • Hello Peter,

    I didn't ask about the "parent" configuration of your air gapped server (AGS). I assumed you were using something like \\AGS\updates and let EM Library pull the stuff from there. I might misunderstand you but it sounds like you were (and are) writing directly to the share(s). When I tested air gapped updating I had configured the AGS to "loop back" to shares created on the removable medium - I've never copied to the "target" shares.

    There's a description for Failed to acquire product information. The article lists common problems and how to resolve them. It might help you to find out what's still missing.

    Christian 

    :10389
Children
No Data