connection failed to Meditech host: ISB Hello failed

Question

Hi We are using Networker Module for Meditech to backup Meditech host DB and we hit to an error to connect to Meditech host We are using Recoverpoint to do the snapshot. however, though the username or password are correctly entered to the Meditech Module, we keep having the same error. it is not able to retrieve the backup list. Networker server installed with: Meditech Module Solution Enabler Navi/Unisphere CLI and agent plink.exe Meditech host: Navi/Unisphere CLI plink.exe below is portion of the error even though we have used the Correct login: nsrmedisv(2336): connect success nmmedicomm.cpp(94): Entering CMedilsbConn::isbconn_hello_request() for nmmedicomm.cpp(124): Sending Hello request to the server... nmmedicomm.cpp(139): send() for Hello succeded for host .<> 51287:nsrmedisv:nmmedicomm(151): Error connecting the ISB host <> Hello answer failed, status:0x00000003 51418:nsrmedisv:nsrmedisv(2346):Connection failed to MEDITECH host<> :ISB HELLO failed. nmmedicomm(918): Error from host<> for Hello Answer: Error 3:ISB Bad Login -- incorrect username or password. Packet type: 0x000000001, Packet size: 0x00000204 nmmedisocket.cpp(331): Entering nmmedi_close_connection() ... If we use the SAN Type as Clariion, the 'Hello' request is successful but waiting for the backup list for very long any advise on the above. Thanks. regards Tuck Chong

tc_chan · Answer

I saw the support matrix has another Meditech Module for Recoverpoint but I can't download it. On top of that, it only support RPA v3.5 and below? is this true?

can anyone advise? thanks.

regards

Tuck Chong

dgold-2014 · Answer

Is this client-server or MAGIC?

I'd suggest you check the SAN History logs on the BG or MAGIC server, and then double check the ISB login on the BG/MAGIC side.

Is this a new install or an existing one that stopped working?

--Dave

tc_chan · Answer

Hi Dave We did check on the listening port 2988 on the BG and it shows state 1 and just exit with error. This is a new setup. Regards Chan

tc_chan · Answer

However if I changed the SAN type to Clariion , it will login and also detect the lun. But with Recoverpoint as the SAN type with the same login, it shows the error.

tc_chan · Answer

Hi Dave We have upgraded the MTSAN.dll to the latest 4.5.13 , if you are referring to that. I was wondering if the Networker Meditech Module could be the cause? Please advise. Thanks.

dgold-2014 · Answer

Hmm...perhaps recoverpoint has a different San DLL? Dave

dgold-2014 · Answer

There are different versions of the mtsan DLL...is yours a clarion or recover point version?

tc_chan · Answer

Recoverpoint infra setup. Currently we are using Meditech Module v3.0build 90 which I think is clariion ver . Is this RPA ver? Mtsan.dll is v4.5.13.

Can advise on the RPA VER? Is it meditech module Ver 8.2?

dgold-2014 · Answer

Don't know, haven't set it up. If you look at the properties of the DLL you

should see cla for clarion.

Contact meditech and ask them for the DLL and setup requirements for

recover point config on their side.

Dg

tc_chan · Answer

Thanks Dave Been trying to contact someone that can help out.

tc_chan · Answer

It is not EMR setup. Its the communication between BG and Meditech module which somehow not up yet .

dgold-2014 · Answer

BTW, the version of NMMedi doesn't change, it is the config on the client

that I'm thinking the issue relates to.

I haven't set up Recoverpoint, but I have configured EVA, FastT and

Clariion. Definitely ask Meditech for the Recoverpoint Dll, and confirm

with them that there isn't any ISB configuration that they need to do that

is separate for Clariion versus Recoverpoint.

If you have an EMR server, you'll find that is the easiest one to start

with, since you can see the ISB listener logs directly, and don't need to

use the menu to view them.

Dave

From: tc.chan

Sent: Friday, June 27, 2014 8:43 AM

To: dave

Subject: Re: - connection failed to Meditech

host: ISB Hello failed

ECN

connection failed to Meditech host: ISB Hello failed

reply from tc.chan

in

*NetWorker

Support Forum* - View the full discussion

dgold-2014 · Answer

I understood that...in my experience, if the site has EMR, it is much

easier to set that up first, since it has its own integrated ISB listener.

Sounds like there is no EMR at your site, so you'll have to proceed with

BG hosting the ISB listener.

Dave

From: tc.chan

Sent: Friday, June 27, 2014 9:25 AM

To: dave

Subject: Re: - connection failed to Meditech

host: ISB Hello failed

ECN

connection failed to Meditech host: ISB Hello failed

reply from tc.chan

in

*NetWorker

Support Forum* - View the full discussion

NetWorker

Was this post helpful?