It is an upgrade. Getting this again. 04:29:11.455 [8891] <16> emmlib_initializeEx: (-) Failed to resolve EMM server reference 04:29:16.456 [8891] <16> vmd: EMM interface initialization failed, status = 195
This is a nightmare. On Wed, 14 Jun 2006, WEAVER, Simon wrote: > > Justin > If this is NOT an upgrade - can you remove and attempt to reinstall again? > > Failing this, what about this link? > > http://seer.support.veritas.com/docs/280401.htm > > Regards > > Simon Weaver > 3rd Line Technical Support > Windows Domain Administrator > > EADS Astrium Limited, B32AA IM (DCS) > Anchorage Road, Portsmouth, PO3 5PU > > Email: [EMAIL PROTECTED] > > > > -----Original Message----- > From: Justin Piszcz [mailto:[EMAIL PROTECTED] > Sent: 14 June 2006 11:19 > To: veritas-bu@mailman.eng.auburn.edu > Subject: Re: [Veritas-bu] Help, NB6.0MP2: EMM interface initialization > failed,status = 77 > > > $ sudo ./nbemmcmd -getemmserver > NBEMMCMD, Version:6.0MP2(20060307) > Library Initialization failed. > CORBA communication error (195) > Command did not complete successfully. > > :( > > On Wed, 14 Jun 2006, Justin Piszcz wrote: > >> Not my day. >> >> 10:11:01.420 [19750] <2> vnet_version_accept: vnetd.c.1133: >> *actual_version: >> 4 0x00000004 >> 10:11:01.452 [19750] <2> ProcessRequests: vnetd.c.336: msg: Request >> VN_REQUEST_SERVICE_SOCKET(6) >> 10:11:01.452 [19750] <2> process_service_socket: vnetd.c.1515: > service_name: >> vmd >> 10:11:05.492 [19750] <2> vnet_connect_by_vnetd: vnet_vnetd.c.1457: status: > 10 >> 0x0000000a >> 10:11:05.492 [19750] <2> process_service_socket: vnetd.c.1568: >> vnet_connect_by_vnetd failed: 10 0x0000000a >> 10:11:05.492 [19750] <2> ProcessRequests: vnetd.c.338: status: 10 > 0x0000000a >> 10:11:05.493 [19750] <2> vnet_pop_byte: vnet.c.163: errno: 111 0x0000006f >> 10:11:05.493 [19750] <2> vnet_pop_byte: vnet.c.164: Function failed: 42 >> 0x0000002a >> 10:11:05.493 [19750] <2> vnet_pop_string: vnet.c.251: Function failed: 42 >> 0x0000002a >> 10:11:05.493 [19750] <2> vnet_pop_signed: vnet.c.301: Function failed: 42 >> 0x0000002a >> 10:11:05.493 [19750] <2> ProcessRequests: vnetd.c.286: vnet_pop_signed >> failed: 42 0x0000002a >> 10:11:05.493 [19750] <2> ListenForConnection: vnetd.c.597: Function > failed: >> 42 0x0000002a >> >> >> On Wed, 14 Jun 2006, Justin Piszcz wrote: >> >>> $ sudo /usr/openv/volmgr/bin/tpconfig -d >>> EMM interface initialization failed, status = 77 >>> >>> Anyone know what may be wrong here? >>> Also have a ticket open with Symantec.. >>> >> > _______________________________________________ > Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu > http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu > > This email is for the intended addressee only. > If you have received it in error then you must not use, retain, disseminate > or otherwise deal with it. > Please notify the sender by return email. > The views of the author may not necessarily constitute the views of EADS > Astrium Limited. > Nothing in this email shall bind EADS Astrium Limited in any contract or > obligation. > > EADS Astrium Limited, Registered in England and Wales No. 2449259 > Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, > England > _______________________________________________ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu