Error Connecting Jobview
Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Information Governance Backup and Recovery Business Continuity Partners Inside Veritas Vision 2016 Developers Blogs Groups Vision 2016 Sign In restart grr server CommunityCategoryBoardResourcesUsers turn on suggestions Auto-suggest helps you quickly narrow down your uninstall grr client search results by suggesting possible matches as you type. Showing results for Search instead for Do you mean VOX : Backup grr rapid response tutorial and Recovery : Backup Exec : BE 2012 on a virtaul machine VOX : Backup and Recovery : Backup Exec : BE 2012 on a virtaul machine Subscribe to RSS Feed Mark Topic grr install as New Mark Topic as Read Float this Topic to the Top Bookmark Subscribe Printer Friendly Page Solved! Go to Solution Highlighted BE 2012 on a virtaul machine Wueff-HH Level 3 Accredited 03-08-2012 04:11 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content Hi Folks, I´m running a Windows 2008 R2 ent Sp1 x64 virtual server. This Server isn´t in a domain. I´ve installed Backup Exec 2012. During the Installation there where absolutely no errors. After starting Bakup Exec i´m able to configure a B2D device. But i can´tsee my own backupserver under the tab "Backup & Recovery". When i´m adding myServer manuallyI Can´t see it, too. In the bottom of Backup Exec, there is a yellow blinkingexclamation point which told me "error connecting JobView" (in german: "Die Abfrage für JobView ist fehlgeschlagen") Any Ideas? greetings, Dennis Solved! Go to Solution. Labels: 2012 Backup and Recovery Backup Exec 0 Kudos Reply 1 Solution Accepted Solutions Accepted Solution! That support tool must run on CraigV Moderator Partner Trusted Advisor Accredited 03-08-2012 05:15 AM Options Mark as New Bookmark Subscribe Subscribe to RSS Feed Highlight Print Email to a Friend Report Inappropriate Content That support tool must run on a domain admin account. If your VM is in a production environment, you could always remove the uplink and leave it as a stand-alone server. This way you can then DCPROMO the server in an isolated environment, and do your testing. But that becomes a non-BE event =) View solution in original post 0 Kudos Reply 4 Replie
Requirements Infrastructure and Security Your User Account Licensing and Billing Branding Agents Features of Windows, OS X, Linux and Mobile Device Agents Managed and OnDemand Agents Deploy Agents Audits Filters and Groups Filters Groups Roles Users Manage Passwords Two-Factor Authentication Account Settings New Device Approval Custom Fields Connection Brokers Agent Updates Profile Settings Proxy Settings in AEM Connection Brokers Local Cache Custom Fields Configuring Third Party Integrations Service Desk Integrations Datto Kaspersky Endpoint Security Splashtop WEB PORTAL Components Download Components http://www.veritas.com/community/forums/be-2012-virtaul-machine Manage Components Create or Edit a Component Deploy Components Using Jobs Profiles Profile Summary Managed and OnDemand Profiles Monitors and Alerts Monitors Alerts Manage Network Management Patch Management iOS Software Management Backup Management Security Management Reports Find the Right Report Schedule and Run a Report Manage Reports Policies Create an Agent Policy Create an iOS Mobile Device Management Policy Create a Monitoring Policy http://help.aem.autotask.net/en/Content/4FEATURESPORTAL/Jobs/JobView.htm Patching Create a Power Policy Create a Security Management Policy Support Create a Ticket in the Web Portal Create a Ticket in the Agent Browser Manage Tickets Devices Device Summary Delete a Device in AEM All Files Deploy Components Using Jobs Manage Jobs Manage Job Alerts The Job View The Job View A user account with the permission to view Scheduled Jobs. System >Monitor >Job Alerts >click on a job Scheduled Jobs >click on a job You can access information about individual jobs both from the Scheduled Jobs page and the System >Monitor >Job Alerts page by clicking on the name of the job. Each device the job was targeted at is represented by a row. By default, all devices are displayed, but you can use the radio buttons to display a specific status only. Columns Field Description Hostname (hyperlink) The name of the device. Click on the name to open the Device Summary page. Refer to Device Summary. Profile The profile the device is associated with. Click on the name to open the Profile Summary page. Refer to Profile Summary. Run at The
Sign in Pricing Blog Support Search GitHub This repository Watch 0 Star 2 Fork 1 KDE/kjobwidgets Code Pull requests 0 https://github.com/KDE/kjobwidgets/blob/master/src/kuiserverjobtracker.cpp Projects 0 Pulse Graphs Permalink Branch: master Switch branches/tags Branches Tags master Nothing to show v5.27.0 v5.27.0-rc1 v5.26.0 v5.26.0-rc1 v5.25.0 v5.25.0-rc1 v5.24.0 v5.24.0-rc1 v5.23.0 v5.23.0-rc1 v5.22.0 v5.22.0-rc1 v5.21.0 v5.21.0-rc2 v5.21.0-rc1 v5.20.0 v5.20.0-rc1 v5.19.0 v5.19.0-rc2 v5.19.0-rc1 v5.18.0 v5.18.0-rc1 v5.17.0 v5.17.0-rc1 v5.16.0 v5.16.0-rc1 v5.15.0 v5.15.0-rc1 v5.14.0 v5.14.0-rc1 v5.13.0 v5.13.0-rc1 v5.12.0 v5.12.0-rc1 v5.11.0 v5.11.0-rc1 v5.10.0 v5.10.0-rc1 v5.9.0 v5.9.0-rc1 error connecting v5.8.0 v5.8.0-rc1 v5.7.0 v5.7.0-rc1 v5.6.0 v5.6.0-rc1 v5.5.0 v5.5.0-rc1 v5.4.0 v5.4.0-rc1 v5.3.0 v5.3.0-rc1 v5.2.0 v5.2.0-rc1 v5.1.0 v5.1.0-rc1 v5.0.0 v5.0.0-rc1 v4.100.0-rc3 v4.100.0-rc2 v4.100.0-rc1 v4.99.0-rc3 v4.99.0-rc1 v4.97.0 v4.96.0 v4.95.0 Nothing to show Find file Copy path kjobwidgets/src/kuiserverjobtracker.cpp Fetching contributors… Cannot retrieve contributors at this time Raw Blame History 334 lines (262 sloc) 9.16 KB /* This file is part error connecting jobview of the KDE project Copyright (C) 2008 Rafael Fernández López