Backup Central

Hi everyone,

out of the blue, i can't start the EMC Networker services anymore.
My OS is Windows Server 2003 x86, the Networker version is 7.3.3

When i try to start the services from Server Manager, it says that the Service did not respond in a timely fashion. When i try to run any networker commands in CMD.exe, i get the errormessage "The ordinal 3249 could not be located in the dynamic link library LIBEAY32.dll.". I get the same Error when i try to start nsrexecd.exe.

I have located LIBEAY32.dll in the ...\nsr\bin folder, it is 1,028,096 bytes, and shows the File Version 0.9.8.7
I tried replacing it temporalily with another version, afterwards some commands (i.e. "inquire", "sjisn") work, but i still can't start the service / nsrexecd.exe. I also installed Networker on another machine to copy the dll, but in the new installation the dll is smaller, and that dll does not work, too.

Using regsvr32.exe to register LIBEAY32.dll does not seem to be possible.

I know that 7.3.3 is quite old, but we don't have a support contract with EMC anymore after we migrated to another backupsoftware roughly two years ago. Until now the Networker always worked when we needed it, but now it's broken. I also can't open a regular request through Powerlink, since 7.3.3 is not listed there anymore.

I hope somebody is able to help me

Best regards,

MPieper

Did you make any changes on your NetWorker server involving SSL? I did a google search for LIBEAY32 and it appears to be used by SSL for encryption purposes.

On 10 26, 2011, at 10:03 AM, MPieper wrote:

Hi everyone,

out of the blue, i can't start the EMC Networker services anymore.
My OS is Windows Server 2003 x86, the Networker version is 7.3.3

When i try to start the services from Server Manager, it says that the Service did not respond in a timely fashion. When i try to run any networker commands in CMD.exe, i get the errormessage "The ordinal 3249 could not be located in the dynamic link library LIBEAY32.dll.". I get the same Error when i try to start nsrexecd.exe.

I have located LIBEAY32.dll in the ...\nsr\bin folder, it is 1,028,096 bytes, and shows the File Version 0.9.8.7
I tried replacing it temporalily with another version, afterwards some commands (i.e. "inquire", "sjisn") work, but i still can't start the service / nsrexecd.exe. I also installed Networker on another machine to copy the dll, but in the new installation the dll is smaller, and that dll does not work, too.

Using regsvr32.exe to register LIBEAY32.dll does not seem to be possible.

I know that 7.3.3 is quite old, but we don't have a support contract with EMC anymore after we migrated to another backupsoftware roughly two years ago. Until now the Networker always worked when we needed it, but now it's broken. I also can't open a regular request through Powerlink, since 7.3.3 is not listed there anymore.

I hope somebody is able to help me

Best regards,

MPieper

+----------------------------------------------------------------------
|This was sent by mpieper < at > roseninspection.net via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

What are you talking about? - is this the NW server or a client?

Ordinal 3249 is the exported function "CRYPTO_is_threading_enabled".
The version I have here that works with 7.3.3 was built against OpenSSL 0.9.7d and size of 798270 bytes.
If replacing the existing dll lets inquire etc work but the service still won't start, it sounds like nsrexecd might be finding a different libeay32.dll on the system somewhere, or not finding the dll at all?

Regards,
Josh

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of MPieper
Sent: Thursday, 27 October 2011 1:04 AM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] Ordinal 3249 not fount in LIBEAY32.dll

Hi everyone,

out of the blue, i can't start the EMC Networker services anymore.
My OS is Windows Server 2003 x86, the Networker version is 7.3.3

When i try to start the services from Server Manager, it says that the Service did not respond in a timely fashion. When i try to run any networker commands in CMD.exe, i get the errormessage "The ordinal 3249 could not be located in the dynamic link library LIBEAY32.dll.". I get the same Error when i try to start nsrexecd.exe.

I have located LIBEAY32.dll in the ...\nsr\bin folder, it is 1,028,096 bytes, and shows the File Version 0.9.8.7
I tried replacing it temporalily with another version, afterwards some commands (i.e. "inquire", "sjisn") work, but i still can't start the service / nsrexecd.exe. I also installed Networker on another machine to copy the dll, but in the new installation the dll is smaller, and that dll does not work, too.

Using regsvr32.exe to register LIBEAY32.dll does not seem to be possible.

I know that 7.3.3 is quite old, but we don't have a support contract with EMC anymore after we migrated to another backupsoftware roughly two years ago. Until now the Networker always worked when we needed it, but now it's broken. I also can't open a regular request through Powerlink, since 7.3.3 is not listed there anymore.

I hope somebody is able to help me

Best regards,

MPieper

+----------------------------------------------------------------------
|This was sent by mpieper < at > roseninspection.net via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Still trying to figure out how to answer this correctly, i'm not used to mailing lists, so i hope the way i used is ok

stan wrote:

Did you make any changes on your NetWorker server involving SSL? I did a google search for LIBEAY32 and it appears to be used by SSL for encryption purposes.
-------
No, i did not change anything regarding the Networker. Only the regular Windows Updates were applied. Also there is an installation of Backup Exec on the server, wich is updated regularly. This parallel installation was never an issue before, this worked for almost 2 years now. Of course we start and stop the respective services when we switch the software.


bingo wrote:

What are you talking about? - is this the NW server or a client?
-------
Sorry if i was not clear enough, i'm sadly not that familiar with networker. I'm talking about Networker Server.


Small, Joshua wrote:

Ordinal 3249 is the exported function "CRYPTO_is_threading_enabled".
The version I have here that works with 7.3.3 was built against OpenSSL 0.9.7d and size of 798270 bytes.
If replacing the existing dll lets inquire etc work but the service still won't start, it sounds like nsrexecd might be finding a different libeay32.dll on the system somewhere, or not finding the dll at all?

Regards,
Josh
-------
When i look at the server with ProcessMonitor, filtered for access of libeay32.dll, nsrexed.exe acesses the correct dll. When i rename the dll in the bin directory, i see that nsrexecd.exe tries various versions of the dll present on the system, until it quits with the error message.

I did a search for libeay32.dll on the server, one version was found in a .cab file of networker, with a size of 798,720 bytes, but there is no version information for this file. When i copied that dll to the bin directory, the error changes, it now can't locate ordinal 3872...

-------
Original Message

Hi everyone,

out of the blue, i can't start the EMC Networker services anymore.
My OS is Windows Server 2003 x86, the Networker version is 7.3.3

When i try to start the services from Server Manager, it says that the Service did not respond in a timely fashion. When i try to run any networker commands in CMD.exe, i get the errormessage "The ordinal 3249 could not be located in the dynamic link library LIBEAY32.dll.". I get the same Error when i try to start nsrexecd.exe.

I have located LIBEAY32.dll in the ...\nsr\bin folder, it is 1,028,096 bytes, and shows the File Version 0.9.8.7
I tried replacing it temporalily with another version, afterwards some commands (i.e. "inquire", "sjisn") work, but i still can't start the service / nsrexecd.exe. I also installed Networker on another machine to copy the dll, but in the new installation the dll is smaller, and that dll does not work, too.

Using regsvr32.exe to register LIBEAY32.dll does not seem to be possible.

I know that 7.3.3 is quite old, but we don't have a support contract with EMC anymore after we migrated to another backupsoftware roughly two years ago. Until now the Networker always worked when we needed it, but now it's broken. I also can't open a regular request through Powerlink, since 7.3.3 is not listed there anymore.

I hope somebody is able to help me

Best regards,

MPieper

I do not really know how to deal with the error message. I would start from the very basics:

- Stop the NW services
- Copy the nsr path to a safe location
- Delete the directories
/nsr/index
/nsr/logs
/nsr/mm
/nsr/res
/nsr/tmp
- Start the NW services (this will result in a fresh installation)
- If NW works now, the program files are fine and the trouble is most likely with the media index
In this case you must recover the last known good bootstrap saveset
- IF NW does not work, reinstall it
Then reactivate the saved databases (forget /nsr/logs & nsr/tmp)

Apart from the final reinstallation step, how will this help resolve a shared library object mismatch?
LIBEAY32.dll is required by LIBRPC.dll - which is used by a lot of the networker binaries.

Using Microsoft's Dependency Walker against nsrexecd.exe, you should be able to spot any DLL issues pretty quickly.
(Hint: press F9 to view the full DLL paths to see where it's finding each one)





-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER < at > LISTSERV.TEMPLE.EDU] On Behalf Of bingo
Sent: Saturday, 29 October 2011 9:17 PM
To: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: [Networker] Ordinal 3249 not fount in LIBEAY32.dll

I do not really know how to deal with the error message. I would start from the very basics:

- Stop the NW services
- Copy the nsr path to a safe location
- Delete the directories
/nsr/index
/nsr/logs
/nsr/mm
/nsr/res
/nsr/tmp
- Start the NW services (this will result in a fresh installation)
- If NW works now, the program files are fine and the trouble is most likely with the media index
In this case you must recover the last known good bootstrap saveset
- IF NW does not work, reinstall it
Then reactivate the saved databases (forget /nsr/logs & nsr/tmp)

+----------------------------------------------------------------------
|This was sent by carsten_reinfeld < at > avus-cr.de via Backup Central.
|Forward SPAM to abuse < at > backupcentral.com.
+----------------------------------------------------------------------


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

Honestly, i do not know as i have never seen this error.
And i can also imagine that the effect (the resulting error message) does not really point to the problem.

But once the software is installed properly, the only thing that prevents the NW server to start is a defective media index.

Honestly, i do not know as i have never seen this error.
And i can also imagine that the effect (the resulting error message)
does not really point to the problem.

But once the software is installed properly, the only thing that
prevents the NW server to start is a defective media index.

I have had 2 NW servers that would not start services until the "nsrladb"
was deleted and rebuilt. A defective media index is not the only thing
that will prevent a NW server from starting.

(these were both NW 7.6.2 servers that had been upgraded from 7.5.2)


via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

@Michael,

this was the exact problem i have encountered on our 400+ clients running NW 7.5.1. Meanwhile, this has been confirmed by EMC. AFAIK these problems will not exist with NW clients of 7.3.0+.