Error 1920 Service Networker Remote
Contents |
SERVICES Services Overview Education Services Business Critical Services Consulting Services Managed Services Appliance Services CUSTOMER CENTER Customer Center Support Community MyVeritas Customer Success Licensing Programs Licensing Process ABOUT About Corporate Profile Corporate Leadership Newsroom Research Exchange error 1920 service networker remote exec service Investor Relations Careers Legal Contact Us English ä¸æ–‡(简体) English Français Deutsch Italiano unable to start networker remote exec service 日本語 í•œêµì–´ Português Español USA Site: Veritas Veritas PartnerNet "Error 1920. Service Backup Exec Remote Agent (Backup Exec Agent
Error 1920. Service Networker Remote Exec Service Failed To Start
Accelerator) failed to start. Verify that you have sufficient privileges to start the services." Article:000008790 Publish: Article URL:http://www.veritas.com/docs/000008790 Support / Article Sign In Remember me Forgot Password? Don't have a Veritas Account?
Error 1920 Service Failed To Start Verify That You Have Sufficient Privileges
Create a Veritas Account now! Welcome First Last Your Profile Logout Sign in to Subscribe Please sign in to set up your subscription. Close Sign In Print Article Products Article Languages Subscribe to this Article Manage your Subscriptions Problem During the installation of the Remote Agent for Windows Servers (RAWS), you get an error: "Error 1920. Service Backup Exec for Remote Agent networker remote exec service not starting (Backup Exec Agent Accelerator) failed to start. Verify that you have sufficient privileges to start the services." In some cases the Remote Agent installs successfully but the service does not start and generates this error. (Figure 1) Error Message Figure 1 Cause This error occurs if another application is using the port 10000. Symantec recommends that port 10000 be used for Network Data Management Protocol (NDMP) communication, as this is the port defined for NDMP by the Internet Assigned Numbers Authority, but the port defined for NDMP can be changed. To change this port, please refer to the Solution section.   Solution On the remote server, verify that the issue is indeed caused by the NDMP port issue by opening a command prompt window and browsing to the Remote Agent for Windows Servers (RAWS) folder which is ideally located in C:\Program Files\Symantec\Backup Exec\RAWS. Now type the command beremote.exe -console It will give the output on the console as follows: The highlighted part indicates that NDMP protocol is not able to use port 10000. Change the port defined for NDMP to a different number e.g. 11000. To do
Join INTELLIGENT WORK FORUMSFOR COMPUTER PROFESSIONALS Log In Come Join Us! Are you aComputer / IT professional?Join Tek-Tips Forums! Talk With Other Members Be Notified Of ResponsesTo Your Posts
Change The Default Timeout On The Windows Services
Keyword Search One-Click Access To YourFavorite Forums Automated SignaturesOn Your Posts Best verify that you have sufficient privileges to start system services Of All, It's Free! Join Us! *Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in error 1920 service office software protection platform osppsvc to receive e-mail. Posting Guidelines Promoting, selling, recruiting, coursework and thesis posting is forbidden.Tek-Tips Posting Policies Jobs Jobs from Indeed What: Where: jobs by Link To This Forum! Add Stickiness To https://www.veritas.com/support/en_US/article.000008790 Your Site By Linking To This Professionally Managed Technical Forum.Just copy and paste the BBCode HTML Markdown MediaWiki reStructuredText code below into your site. Legato back-up solutions Forum at Tek-Tips HomeForumsServer RackBack-up SystemsLegato back-up solutions Forum Error 1920.Service 'nsrexecd'(nsrexecd)failed to start.Verify that you thread480-1606156 Forum Search FAQs Links MVPs Error 1920.Service 'nsrexecd'(nsrexecd)failed to start.Verify that you Error 1920.Service 'nsrexecd'(nsrexecd)failed to start.Verify that http://www.tek-tips.com/viewthread.cfm?qid=1606156 you emcproduct (Vendor) (OP) 30 May 10 07:12 Hi Guys,I'd like to ask your help with this problem, I've tried installing networker 7.6 on windows 2003 server (cluster environment) but during installation the error.... "Error 1920.Service (nsrexecd)failed to start.Verify that you have sufficient privileges to start system services". What would be the problem? I have the used the domain admin account already and try to restart the service using manual domain admin account.Kindly give me your opinion, Any help would be appreciated.Thanks RE: Error 1920.Service 'nsrexecd'(nsrexecd)failed to start.Verify that you wallace88 (TechnicalUser) 5 Jun 10 14:34 Did the installation complete, or did it roll out and not install?Does task manager show a nsrexecd.exe running?Was there a "NetWorker Remote Exec Service" in the list of services?These would tell you if NetWorker was successfully installed as a service.By default, the "NetWorker Remote Exec Service" (nsrexecd) is started using the local system account.You can change this to use a different account after the install completes.How did you manually restart?(Re)starting nsrexecd as a service is different that running nsrexecd from command line.Using your domain admin account, type nsrexecd from command
FAQForumsJoin Our Forums!General TopicsBakBone NetVaultCA Brighstor ARCserveCommVault GalaxyEMC NetWorkerHP Data ProtectorIBM TSMSymantec Backup ExecSyncSort Backup ExpressSymantec NetBackupOpen-Source AmandaOpen-Source BackupPCOpen-Source BaculaOpen-Source Rdiff-BackupOpen-Source RsnapshotWikiRecent ChangesSpecial PagesPopular PagesCategoriesContact CurtisYour AccountYour DetailsMaintain SiteLogoutYours Search • FAQ • Memberlist • Log in Backup Central https://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/emc-networker-19/unable-to-start-nsrexecd-when-upgrading-windows-2003-server-122590/ Forums Forum Index » EMC NetWorker » Unable to start nsrexecd when upgrading windows 2003 server The time now is Mon Oct 10, 2016 7:22 am View previous topic | View next topic Page 1 of 1 Unable to start nsrexecd when upgrading windows 2003 server Author Message Roberts, Justin (GE, A... Guest Unable to start nsrexecd when upgrading error 1920 windows 2003 server We are currently upgrading our environment from 7.6 to 8.0. On several occasions when installing 8.0 client on 32-bit Windows 2003 servers the install gets to the end and is unable to start the services. It throws an error "1920, the account does not have the privileges to start services". We've been working with EMC on this error 1920 service and so far none of the solutions they have provided seem to work. Has anyone ever seen this before? Thanks Justin M Roberts Wed Sep 11, 2013 6:58 am bingo Joined: 27 Jul 2007 Posts: 663 Unable to start nsrexecd when upgrading windows 2003 server If you have verified that the service runs as "Local System" account, i am pretty sure that deleting/renaming the ..\nsr\res\nsrladb directory will resolve the issue. I have had a bunch of problems when (remotely) updating NW 7.5/7.6 clients. Don't remember the exact problem any more. However i figured out that NW obviously has problems to read/convert the old config files. Thu Sep 12, 2013 1:17 am FAIDHERBE Thierry Guest Unable to start nsrexecd when upgrading windows 2003 server You can also try to start nsrexecd in debug, to see where it fails Log as local admin and launch nsrexecd -D 9 from %install_dir%\bin HTH TH Kind regards - Bien cordialement - Vriendelijke groeten, Thierry FAIDHERBE Backup/Storage & System Management LE FOREM Département des Systèmes d'Information Direction Infrastructure Boulevard Tirou, 104 Tel: