I believe you are suffering from a known issue (ref NW113839). I would open a Support call and request the hot fix.
Regards,
Bill Mason
SME - Advanced Technical Support
EMC Global Services
Problem Resolution and Escalation Management (PREM)
BURA Software Solutions Group (BSSG)
Office: 44 (0) 208-758-6452
North America Support Line: 1-877-534-2867
mason_bill@emc.com
Please note my regular working hours are Monday to Friday, 07:30am to 14:00 pm GMT, 16:00 pm to 18:00 pm GMT
Please submit all new cases, updates or attachments to existing cases via EMC Powerlink http://powerlink.emc.com/
For new issues & questions, EMC Customer Service is pleased to offer you the support option of Live Chat 24x7 for select products.
To interact with our technical support professionals please visit the Networker Support landing page and select ‘Live Chat’ under Additional Resources.
For a single location for you to gain access to all key Support-related resources on Powerlink related to Networker & Avamar, please check out the appropriate landing page:
EMC Networker Support landing page at: https://support.emc.com/products/NetWorker
EMC Avamar Support landing page at: https://support.emc.com/products/Avamar
Satisfied customers are my top priority. For service feedback & comments, please contact my manager:
This looks like a known issue concerning lockboxes with NMO - reference NW113839 - 'Lockbox unusable after Networker upgrade - client creation fails'. It involves a situation where the lockbox resource inside in NetWorker is deleted. This will be fixed in later NetWorker versions. In the meantime, you should be able to workaround this by deleting the lockbox for this client from the file system which would be in for example 'C:\Program Files\Legato\nsr\lockbox\[client_name]'. The problem is created by the fact that the lockbox resource no longer exists in NetWorker but exists in the file system. Let me know if this works.
Powerlink will provide you with a solution soon but currently its not available to Customers as Bobby is still writing the content, which references the escalation but gives no details of what our engineers did. Usually escalation details are not made available outside EMC. It will detail what the symptoms are, why they are seen and what to do to resolve which may include a workaround or direct you to a specific Cumulative release of the software (we release interim software packages which contain hot fixes which have been verified to date) which has the hot fix within it or ask you to raise a support call to get the fix from us.
Regards,
Bill Mason
SME - Advanced Technical Support
EMC Global Services
Problem Resolution and Escalation Management (PREM)
BURA Software Solutions Group (BSSG)
Office: 44 (0) 208-758-6452
North America Support Line: 1-877-534-2867
mason_bill@emc.com
Please note my regular working hours are Monday to Friday, 07:30am to 14:00 pm GMT, 16:00 pm to 18:00 pm GMT
Please submit all new cases, updates or attachments to existing cases via EMC Powerlink http://powerlink.emc.com/
For new issues & questions, EMC Customer Service is pleased to offer you the support option of Live Chat 24x7 for select products.
To interact with our technical support professionals please visit the Networker Support landing page and select ‘Live Chat’ under Additional Resources.
For a single location for you to gain access to all key Support-related resources on Powerlink related to Networker & Avamar, please check out the appropriate landing page:
EMC Networker Support landing page at: https://support.emc.com/products/NetWorker
EMC Avamar Support landing page at: https://support.emc.com/products/Avamar
Satisfied customers are my top priority. For service feedback & comments, please contact my manager:
I did uninstalled the NMO. I deleted the directory lockbox and then install the NMO again, with this a new directory lockbox was created but the problem persist.
masonb
445 Posts
0
April 28th, 2010 00:00
AngeLinux,
I believe you are suffering from a known issue (ref NW113839). I would open a Support call and request the hot fix.
Regards,
Bill Mason
SME - Advanced Technical Support
EMC Global Services
Problem Resolution and Escalation Management (PREM)
BURA Software Solutions Group (BSSG)
Office: 44 (0) 208-758-6452
North America Support Line: 1-877-534-2867
mason_bill@emc.com
Please note my regular working hours are Monday to Friday, 07:30am to 14:00 pm GMT, 16:00 pm to 18:00 pm GMT
Please submit all new cases, updates or attachments to existing cases via EMC Powerlink http://powerlink.emc.com/
For new issues & questions, EMC Customer Service is pleased to offer you the support option of Live Chat 24x7 for select products.
To interact with our technical support professionals please visit the Networker Support landing page and select ‘Live Chat’ under Additional Resources.
For a single location for you to gain access to all key Support-related resources on Powerlink related to Networker & Avamar, please check out the appropriate landing page:
EMC Networker Support landing page at: https://support.emc.com/products/NetWorker
EMC Avamar Support landing page at: https://support.emc.com/products/Avamar
Satisfied customers are my top priority. For service feedback & comments, please contact my manager:
Mary ODonoghue - ODonoghue_Mary@emc.com
coganb
736 Posts
0
April 28th, 2010 01:00
This looks like a known issue concerning lockboxes with NMO - reference NW113839 - 'Lockbox unusable after Networker upgrade - client creation fails'. It involves a situation where the lockbox resource inside in NetWorker is deleted. This will be fixed in later NetWorker versions. In the meantime, you should be able to workaround this by deleting the lockbox for this client from the file system which would be in for example 'C:\Program Files\Legato\nsr\lockbox\[client_name]'. The problem is created by the fact that the lockbox resource no longer exists in NetWorker but exists in the file system. Let me know if this works.
-Bobby
AngeLinux1
17 Posts
0
April 28th, 2010 08:00
Thanks William
Where can I search information about this known issue (ref NW113839) in powerlink?? in what link??
Thanks again
-
Angel
AngeLinux1
17 Posts
0
April 28th, 2010 08:00
Thanks Bobby
This problem is with a NetworkerServer SP2, in Linux Server. I guess this is in /nsr/lockbox/[hostname_nwclient_oracle]
I will find this directory and tell you the results
Thanks
--
Angel
masonb
445 Posts
0
April 28th, 2010 10:00
Angel,
Powerlink will provide you with a solution soon but currently its not available to Customers as Bobby is still writing the content, which references the escalation but gives no details of what our engineers did. Usually escalation details are not made available outside EMC. It will detail what the symptoms are, why they are seen and what to do to resolve which may include a workaround or direct you to a specific Cumulative release of the software (we release interim software packages which contain hot fixes which have been verified to date) which has the hot fix within it or ask you to raise a support call to get the fix from us.
Regards,
Bill Mason
SME - Advanced Technical Support
EMC Global Services
Problem Resolution and Escalation Management (PREM)
BURA Software Solutions Group (BSSG)
Office: 44 (0) 208-758-6452
North America Support Line: 1-877-534-2867
mason_bill@emc.com
Please note my regular working hours are Monday to Friday, 07:30am to 14:00 pm GMT, 16:00 pm to 18:00 pm GMT
Please submit all new cases, updates or attachments to existing cases via EMC Powerlink http://powerlink.emc.com/
For new issues & questions, EMC Customer Service is pleased to offer you the support option of Live Chat 24x7 for select products.
To interact with our technical support professionals please visit the Networker Support landing page and select ‘Live Chat’ under Additional Resources.
For a single location for you to gain access to all key Support-related resources on Powerlink related to Networker & Avamar, please check out the appropriate landing page:
EMC Networker Support landing page at: https://support.emc.com/products/NetWorker
EMC Avamar Support landing page at: https://support.emc.com/products/Avamar
Satisfied customers are my top priority. For service feedback & comments, please contact my manager:
Mary ODonoghue - ODonoghue_Mary@emc.com
AngeLinux1
17 Posts
0
May 5th, 2010 12:00
Bobby
I did uninstalled the NMO. I deleted the directory lockbox and then install the NMO again, with this a new directory lockbox was created but the problem persist.
Some other tip, for solve this problem??
-
Thanks for your assistance
Angel
Holger_Inf
1 Rookie
•
122 Posts
0
May 6th, 2010 00:00
some people already told you:
open a support case with EMC, ask for csp-lb.dll from the mentioned bug number
stop your networker server and client service on the server, replace this file in two
locations on the server (networkert and nmc bin directory), rename nsr\lockboxes\ directory
to something else
and start nsrexecd
compare the renamed with the newly created dir, the renamed contaion one zero byte file, the
new dir contain four files.
And you you can use your lockbox.
This was as it worked with my server