{"id":1985,"date":"2014-05-09T21:11:35","date_gmt":"2014-05-09T20:11:35","guid":{"rendered":"http:\/\/www.data-protector.org\/wordpress\/?p=1985"},"modified":"2015-12-09T18:07:34","modified_gmt":"2015-12-09T17:07:34","slug":"internal-error-launching-dp-gui","status":"publish","type":"post","link":"https:\/\/www.data-protector.org\/wordpress\/2014\/05\/internal-error-launching-dp-gui\/","title":{"rendered":"Internal error when launching DP GUI"},"content":{"rendered":"<p>After a new installation of Data Protector and when the GUI is opened you might receive a &#8220;Internal Error&#8221; message. In this case the GUI cannot be used. It seems Windows 8.1 systems are involved. For more details and the solution please visit <a href=\"http:\/\/www.syncer.de\/?p=680\">http:\/\/www.syncer.de\/?p=680<\/a>. Thanks to Sebastian.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>After a new installation of Data Protector and when the GUI is opened you might receive a &#8220;Internal Error&#8221; message. In this case the GUI cannot be used. It seems Windows 8.1 systems are involved. For more details and the solution please visit http:\/\/www.syncer.de\/?p=680. Thanks to Sebastian.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_mi_skip_tracking":false,"spay_email":""},"categories":[24],"tags":[],"translation":{"provider":"WPGlobus","version":"2.8.8","language":"en","enabled_languages":["en","de"],"languages":{"en":{"title":true,"content":true,"excerpt":false},"de":{"title":false,"content":true,"excerpt":false}}},"jetpack_featured_media_url":"","jetpack_shortlink":"https:\/\/wp.me\/p28cjj-w1","jetpack_sharing_enabled":true,"jetpack-related-posts":[{"id":1665,"url":"https:\/\/www.data-protector.org\/wordpress\/2013\/11\/data-protector-8-1-unveiled\/","url_meta":{"origin":1985,"position":0},"title":"Data Protector 8.1 unveiled","date":"22. November 2013","format":false,"excerpt":"{:en}HP has let the cat out of the bag and unveiled the next version of HP Data Protector 8.1. Some new cool stuff will be added and of course the platform and integration enhancements we already have seen with DP 7.03. The new \"advanced\" scheduler will be my favorite. And\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2095,"url":"https:\/\/www.data-protector.org\/wordpress\/2014\/08\/add-licenses-data-protector\/","url_meta":{"origin":1985,"position":1},"title":"How to add licenses in Data Protector","date":"25. August 2014","format":false,"excerpt":"{:en}There are different ways to add licenses into Data Protector. Copy and paste the license file generated on the licensing portal (http:\/\/www.webware.hp.com) as ...\/Config\/Server\/cell\/lic.dat Copy and paste of a single or several licenses keys into exisiting lic.dat Copy and paste of a single license key using the Data Protector GUI\u2026","rel":"","context":"In &quot;BASICS&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":126,"url":"https:\/\/www.data-protector.org\/wordpress\/2010\/08\/enhanced-automated-disaster-recovery\/","url_meta":{"origin":1985,"position":2},"title":"Enhanced Automated Disaster Recovery","date":"6. August 2010","format":false,"excerpt":"{:en}No translation for this article available.{:} {:de} Immer wieder mal ben\u00f6tigt man es wenn ein Server komplett den Bach runter geht... \u00a0In der Regel sollte man vor einem Disaster wissen wie man seine Server wieder herstellt. In den Unterlagen von HP ist zwar sehr sch\u00f6n und ausf\u00fchrlich beschrieben welche einzelnen\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":150,"url":"https:\/\/www.data-protector.org\/wordpress\/2011\/07\/reorganisation-der-internen-datenbank\/","url_meta":{"origin":1985,"position":3},"title":"Internal Database error &#8211; reorganize your IDB","date":"15. July 2011","format":false,"excerpt":"{:en}Update: There are still a lot of old Data Protector installations (version 6.0, 6.1) and in all cases I've seen there is still the old errror described below. Thats why I updated and enhanced this article from August 2010. When updating from a former Data Protector (5.X to 6.0 to\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":1183,"url":"https:\/\/www.data-protector.org\/wordpress\/2012\/11\/dp-701-patch-bundle-unix-cell-server-mom-environment\/","url_meta":{"origin":1985,"position":4},"title":"DP 701 patch bundle on Unix Cell Server in MoM environment","date":"21. November 2012","format":false,"excerpt":"{:en}During the installation of patch bundle DPUXBDL_00701 in a MoM environment the installation might fail and the dedupe and the core patch cannot be installed. When checking with swinstall you will get the information that the pre checks were not successful. The error has been seen in an environment with\u2026","rel":"","context":"In &quot;Common&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]},{"id":2190,"url":"https:\/\/www.data-protector.org\/wordpress\/2015\/01\/eadr-tape-block-size\/","url_meta":{"origin":1985,"position":5},"title":"EADR and Tape Block Size","date":"1. January 2015","format":false,"excerpt":"{:en}In older articles I often wrote about Bare Metal Recovery, a feature included in Data Protector without any additional costs and called Enhanced Automated Disaster Recovery (EADR) - see https:\/\/www.data-protector.org\/wordpress\/?s=eadr. To recover the Cell Server (see link) I always told to use tape devices with a block size of 64K.\u2026","rel":"","context":"In &quot;HowTo&quot;","img":{"alt_text":"","src":"","width":0,"height":0},"classes":[]}],"_links":{"self":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1985"}],"collection":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/comments?post=1985"}],"version-history":[{"count":2,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1985\/revisions"}],"predecessor-version":[{"id":2563,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/posts\/1985\/revisions\/2563"}],"wp:attachment":[{"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/media?parent=1985"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/categories?post=1985"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.data-protector.org\/wordpress\/wp-json\/wp\/v2\/tags?post=1985"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}