Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it!  Learn more

  • State Suggested Answer
  • Replies replies
    2
  • Answers answer
    1
  • Subscribers subscribers
    204
  • Views views
    189
  • Users 0 members are here
Related
Options

OBM windows server certificate not received

Vivek Kaushik

Hello I am successful run oaistall.vbs file on window server but I didn't get certificate request in OBM .

  • Suggested Answer

    0  

    Hello Vivek

    Have you already ran the opcativate tool to configure the agent?

    Personally I had no success when doing the installation and configuration on a single string so after running the oainstall tool we can run the opcatviate.vbs script with the parameter -srv <GW FQND> to configure the agent.

    Tool is located at %ovinstalldir%\bin\win64\OpC\install\

    Additionally please check that the ovcs service is running on your DPS server with the command ovc -status

    if the service is not running start it with ovc -start ovcs and run the ovcert -certreq command on the manage node to request the certificate.

    if the agent has been configured and the ovcs service is running and you still not see the certificate on the ui try the command line option on the DPS run ovcm -listpending -l and see if the certificate request from your manage node shows there if yes you can do ovcm -grant <request id> to grant the certificate.

    If the above validations don't help is better to open a support ticket for deeper troubleshooting

  • 0  

    Maybe you can check if there is a firewall running somewhere between the agent and the OBM server itself.

    You can use this PowerShell to check:

    $server = "servername.com"
    $port = 383

    $tcpClient = New-Object System.Net.Sockets.TcpClient

    try {
         $tcpClient.Connect($server, $port)

        if ($tcpClient.Connected) {
          Write-Host "Port $port is open on $server."
        } else {
          Write-Host "Port $port is closed on $server."
        }
    } catch {
          Write-Host "Port $port is closed on $server."
          Write-Host $_.Exception.Message
    } finally {
       if ($tcpClient.Connected) {
          $tcpClient.Close()
       }
    }

    I'd also use "ovcert -remove" to remove any old certificated before running "ovcert -certreq".

    I hope this helps.

    --
    If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.