10-08-2013 04:12 AM
I have just installed DP 8.0 CM on Linux and GUI on my Windows 7 client.
It seems to work fine, but I cannot configure or query any device.
If I click on "Devices" under "Devices & Media" menu I get an "Insufficient permissions, access denied." error message.
I'm connecting DP using an admin user, so I don't understand why I get this error message.
What I'm missing?
10-08-2013 06:26 AM
I found these messages in /var/opt/omni/log/AppServer/DPServer.log every time I click on "Devices":
15:23:59,761 ERROR [BaseAuthenticator:150:http--0.0.0.0-7116-1] Ticket is null!
15:23:59,828 ERROR [DpAuthenticateResource:136:http--0.0.0.0-7116-1] forbidden.
15:23:59,834 ERROR [BaseAuthenticator:150:http--0.0.0.0-7116-1] Ticket is null!
15:23:59,896 ERROR [DpAuthenticateResource:136:http--0.0.0.0-7116-1] forbidden.
15:23:59,902 ERROR [BaseAuthenticator:150:http--0.0.0.0-7116-1] Ticket is null!
15:23:59,947 ERROR [BaseAuthenticator:150:http--0.0.0.0-7116-1] Ticket is null!
15:24:00,011 ERROR [DpAuthenticateResource:136:http--0.0.0.0-7116-1] forbidden.
15:24:00,017 ERROR [BaseAuthenticator:150:http--0.0.0.0-7116-1] Ticket is null!
15:24:00,085 ERROR [DpAuthenticateResource:136:http--0.0.0.0-7116-1] forbidden.
15:24:00,092 ERROR [BaseAuthenticator:150:http--0.0.0.0-7116-1] Ticket is null!
It seems AppServer has some kind of problem.
10-08-2013 07:35 AM
Did you do this prior to installing DP 8.0:
On Linux and HP-UX, the database OS super user must be created prior to
the installation. The recommendation on Linux and HP-UX is to name it as
and to create a user group (with the same name) hpdp that the user
10-08-2013 08:00 AM
Yes, I did.
Following processes status:
[root@backupsrv ~]# omnisv status
ProcName Status [PID]
crs : Active 
mmd : Active 
kms : Active 
hpdp-idb : Active 
hpdp-idb-cp : Active 
hpdp-as : Active 
omnitrig : Active
Sending of traps disabled.
Status: All Data Protector processes/services up and running.
[root@backupsrv ~]# ps -ef | grep omni
hpdp 3760 1 0 16:56 ? 00:00:00 /opt/omni/idb/bin/postgres -D /var/opt/omni/server/db80/pg
hpdp 3785 1 0 16:56 ? 00:00:00 /opt/omni/idb/bin/pgbouncer -d /etc/opt/omni/server/idb//hpdp-idb-cp.cfg
root 3789 1 0 16:56 ? 00:00:00 /opt/omni/lbin/mmd -session_key 1001 -owner root root backupsrv 3788 4294967295 -lang C
root 3790 1 0 16:56 ? 00:00:00 /opt/omni/lbin/kms -session_key 1002 -owner root root backupsrv 3788 4294967295 -lang C
root 3791 1 0 16:56 ? 00:00:00 /opt/omni/lbin/crs
hpdp 3832 1 0 16:56 ? 00:00:00 /bin/sh /opt/omni/AppServer/bin/standalone.sh -b backupsrv
hpdp 3892 3832 21 16:56 ? 00:00:09 /opt/omni/jre/bin/java -D[Standalone] -server -XX:+UseCompressedOops -XX:+TieredCompilation -Xms64m -Xmx512m -XX:MaxPermSize=256m -Djava.net.preferIPv4Stack=false -Djava.net.preferIPv6Stack=true -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -Djboss.modules.system.pkgs=org.jboss.byteman -Djava.awt.headless=true -Djboss.server.default.config=standalone.xml -Dorg.jboss.boot.log.file=/var/opt/omni/log/AppSer
10-08-2013 08:19 AM
OK, one more thing to see if thsi is only a GUI problem. From the command line on the cell manager, please run
omnidownload -list_devices -detail
This is the command-line equivalent of clicking on Devices in the GUI. If you get the same error, you will need to open a case with teh REsponse Center
10-08-2013 09:38 AM - edited 10-08-2013 09:38 AM
Thank you Bob,
it seems to be a GUI problem:
[root@backupsrv ~]# omnidownload -list_devices -detail
DATAFORMAT NDMP Celerra
Now the question is: How can I fix this GUI problem?
10-08-2013 10:01 AM
I think that it is time to open a case with the response center. To get a head start, in addition to supplying the DP version and the OS-version of the Cell Manager and the system running the GUI, they will be asking you to create debugs. Stop the GUI. On the Cell Manager, clear the file
On the system running the GUI, from the MS-DOS prompt
cd \Program Files\Omniback\bin
manager.exe -debug 1-500 GUI.txt
Duplicate the error, take a screenshot of the error, and exit the GUI
On the system running the GUI,
check the folder
Program Files -> Omniback -> tmp Windows 2003
Program Data -> Omniback -> tmp Windows 2008
Look for long filenames that start OB2DBG and end with GUI.txt. Save these to a ‘zip’ file
On your Cell Manager, check /tmp. Look for long filenames that start OB2DBG and end with GUI.txt. Save these to a 'tar', 'rar', or 'zip' file, along with a copy of the DPServer.log file
Once you get the case opened, ask for a FTP site to be created to send these files to. Hopefully, this will speed things along
10-10-2013 04:02 AM
Thank you all for your replies, but I was testing DP 8 as the first step of an upgrade. This is a test server with no license so I cannot open a service request.
But I don't think I'll upgrade from DP 7 to 8.
I'll wait for some patch to be released.
Meanwhile, I'll be waiting for some other suggestion...
10-10-2013 08:21 AM
Excellent idea, I always advise that you try to hold off on updating until , at lease, the first set of patches are released
Lets just say that DP 8 has had some 'challenges'
10-10-2013 08:33 AM
please keep in mind that you have to wait until December/January timeframe for updates of DP 8.0, which will not be distributed via patches, it will be the 8.1 version.
Please assign Kudos - How to assign...
10-10-2013 10:04 AM
I'm with the same problem, but I noticed that logging in with Windows Domain User which is used to perform the backups on clients, devices and pools are successfully displayed. I will wait for the update to see if problem is solved.
10-11-2013 02:05 AM
unfortunatelly it is not possible for me to logon using same domain user used for backup.
My CellManager is a Linux box and all backed up servers are Linux or Unix.
11-01-2013 08:35 AM - edited 11-01-2013 08:44 AM
It is DNS problem and OmniInet problem.
What is required to correct function:
a. DNS entries for GUI and CellManager - this can be little bit difficult when management station is from different domain in that case you have two options. First: create on DNS server (windows) new zone with domain with Cell Manager, Second: Edit hosts file on Cell Manager /etc/hosts
It must pass: ping fqdn_name_of_gui_client from Cell Manager ping fqdn_name_of_CellManager from Gui Client
and must pass: ping NETBIOS_name_gui_client from CellManager
b. OmniInet service must be running
c. Firewall must allow to pass all communication (on given ports) between CellManager and Gui Client.
Its very weird.
AVE BOHEMIA, s.r.o.
12-24-2013 01:11 PM
This error also happened to me. but the problem was that I was using a laptop via wifi ... when I put the network cable and used a fixed IP I managed to add the device.
02-08-2014 05:57 AM
Hello, I have the same problem with DP 8.1
Environment newly installed. Anyone solved this problem?
In my case already checked the services, DNS, etc, all OK.
02-10-2014 07:19 AM
I had put this question to the lab, and it looks like there is some kid of bug in teh Certificat5e program
could be that certificate expired? They probably all installed after 19th January?
Best to analyze is by simple going taking a browser and open the site:
https://hostname:7116" \t "_blank">https://hostname:7116
It will ask whether it is allowed to continue, then a click on the certificate symbol just before or after the address bar, will show you the certificate. This way you can see whether the certificate is expired
we have a parsing bug in the omnigencert.pl and that procedure below does not work, since it always takes default value.
To fix customer case, there might be many, follow the following procedure:
Find in /etc/opt/omni/client/components/webservice.propert
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>
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 '