DP 8.1 Insufficient permissions, access denied when starting the gui

We have installed a small environment to test DP 8.1.  The environment consists of:

 

1 * AD server (Windows 2003 EE x64)

1 * DP8.1 (Windows 2008 R2 x64)

1 * client (Windows 2008 R2 x64)

 

DNS is running, and resolves all hosts in all directions.

DP services: CRS, IDB & IDB connection pool are running under a domain account

DP service Inet is running under a local system account.

 

When we start the DP gui, the Cell Manager name (fqdn) is already entered in the 'Connect to a Cell Manager' screen.  We select 'Connect', and are then presented with a window to Accept a new certificate.  We do 'OK', and are then asked to enter User name and Password.

 

Whatever we enter here we get the error - 'Insufficient permissions, access denied.' and get no further.

We have tried editing the userlist file, but this made no difference.

 

 

Tags:

Parents
  • Log in as the user who installed DP on the system.  Then edit the users from within the DP GUI to add the needed logins.  DP only puts in the user who installed DP and/or the user used for the DP service when installed.

  • Thanks for your response.

    We tried the suggestion, but it made no difference.  Even though the installation of DP had shown as successful, we decided to re-install it.  This time it worked ok and we can access via the gui.

  • This is becuase of some java process using the port 7116.

    check:

    C:\Users\Administrator>netstat -bano | findstr 7116

    C:\Users\Administrator>netstat -bano | findstr 7116

    C:\Users\Administrator>taskkill /IM java.exe /T /F

    C:\Users\Administrator>taskkill /IM javaw.exe /T /F

     

    and restart services or re-install DP ..this issue will get resolve.

  • In addition to the other suggestions, I had opened a lab case on this issue

     

    ==============

     

    To fix customer case, there might be many, follow the following procedure:

    • Find in /etc/opt/omni/client/components/webservice.properties the keystore password
    • cd to /opt/omni/sbin directory
    • regenerate the certificate using the following command:
    • perl omnigencert.pl –server_id <FQDN of your server> -user_id hpdp -store_password <Your keystore password> -cert_expire <number of days less than 24 * 365>
    • omnisv stop
    • omnisv start

    Alternatively, for now, just search the perl script for '24 * 365' and replace it with '10 * 365'.

    There is going to be a corrected version of  'omnigencert.pl '

  • In addition to the other suggestions, I had opened a lab case on this issue

     

    ==============

     

    To fix customer case, there might be many, follow the following procedure:

    • Find in /etc/opt/omni/client/components/webservice.properties the keystore password
    • cd to /opt/omni/sbin directory
    • regenerate the certificate using the following command:
    • perl omnigencert.pl –server_id <FQDN of your server> -user_id hpdp -store_password <Your keystore password> -cert_expire <number of days less than 24 * 365>
    • omnisv stop
    • omnisv start

    Alternatively, for now, just search the perl script for '24 * 365' and replace it with '10 * 365'.

    There is going to be a corrected version of  'omnigencert.pl '

  • In addition to the other suggestions, I had opened a lab case on this issue

     

    ==============

     

    To fix customer case, there might be many, follow the following procedure:

    • Find in /etc/opt/omni/client/components/webservice.properties the keystore password
    • cd to /opt/omni/sbin directory
    • regenerate the certificate using the following command:
    • perl omnigencert.pl –server_id <FQDN of your server> -user_id hpdp -store_password <Your keystore password> -cert_expire <number of days less than 24 * 365>
    • omnisv stop
    • omnisv start

    Alternatively, for now, just search the perl script for '24 * 365' and replace it with '10 * 365'.

    There is going to be a corrected version of  'omnigencert.pl '

Reply
  • In addition to the other suggestions, I had opened a lab case on this issue

     

    ==============

     

    To fix customer case, there might be many, follow the following procedure:

    • Find in /etc/opt/omni/client/components/webservice.properties the keystore password
    • cd to /opt/omni/sbin directory
    • regenerate the certificate using the following command:
    • perl omnigencert.pl –server_id <FQDN of your server> -user_id hpdp -store_password <Your keystore password> -cert_expire <number of days less than 24 * 365>
    • omnisv stop
    • omnisv start

    Alternatively, for now, just search the perl script for '24 * 365' and replace it with '10 * 365'.

    There is going to be a corrected version of  'omnigencert.pl '

Children
No Data