DSXchange

Hi All

I am having trouble in setting up access for one of my team members. We keep running into the error message pasted below

Also, below are the checks i have made

1. Uninstalled and re-installed the client after cleaning the registry entries
2. listed the IP address in Hosts file
3. ping and telnet from cmd line are able to talk to the host in question

Is there anything else i should be doing to get the issue resolved. The same user id works on other machines without issues. So there is something wrong in this particular machine, which i am unable to figure out

Thanks in advance
Srividya


Failed to connect to Information Server Engine: HLTIXXX, project: USOP_MED_XXX.

(The host name specified is not valid, or the host is not responding (81011))

This error occurred on 11/29/2012 at 10:07 AM (Standard format: 2012/11/29 10:07:34)

Product Version: 8.7.0.0
Client tag: 593456d0-c3dc-4f4b-846f-0d8662ce64bf
Application: director.exe (PID 6868)
Operating System: Windows XP 5.1 Service Pack 3
.NET Framework version: 4.0.30319.296
Machine Name: GXXXYY086530
User Name: XX179K
Language: English (United States)
Time Zone: Eastern Daylight Time

Error message:
Failed to connect to Information Server Engine: HLTIXXX, project: USOP_MED_XXX.

(The host name specified is not valid, or the host is not responding (81011))


Loaded modules:
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.GdiPlus_6595b64144ccf1df_1.0.6002.22791_x-ww_c8dff154\gdiplus.dll 5.2.6002.22791
C:\WINDOWS\WinSxS\x86_Microsoft.Windows.Common-Controls_6595b64144ccf1df_6.0.2600.6028_x-ww_61e65202\comctl32.dll 6.0.2900.6028
C:\WINDOWS\WinSxS\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_d495ac4e\MSVCR90.dll 9.0.30729.4148
C:\WINDOWS\WinSxS\x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.30729.4148_x-ww_d495ac4e\MSVCP90.dll 9.0.30729.4148
C:\WINDOWS\system32\xpsp2res.dll 5.1.2600.5512
C:\WINDOWS\system32\WSOCK32.DLL 5.1.2600.5512
C:\WINDOWS\System32\wshtcpip.dll 5.1.2600.5512
C:\WINDOWS\system32\WS2HELP.dll 5.1.2600.5512
C:\WINDOWS\system32\WS2_32.dll 5.1.2600.5512
C:\WINDOWS\system32\WLDAP32.dll 5.1.2600.5512
C:\WINDOWS\System32\winrnr.dll 5.1.2600.5512
C:\WINDOWS\system32\VERSION.dll 5.1.2600.5512
C:\WINDOWS\system32\uxtheme.dll 6.0.2900.5512
C:\WINDOWS\system32\userenv.dll 5.1.2600.5512
C:\WINDOWS\system32\USER32.dll 5.1.2600.5512
C:\WINDOWS\system32\SXS.DLL 5.1.2600.5512
C:\WINDOWS\system32\SHLWAPI.dll 6.0.2900.5912
C:\WINDOWS\system32\shfolder.dll 6.0.2900.5512
C:\WINDOWS\system32\SHELL32.dll 6.0.2900.6242
C:\WINDOWS\system32\Secur32.dll 5.1.2600.5753
C:\WINDOWS\system32\scrrun.dll 5.7.0.16599
C:\WINDOWS\system32\rsaenh.dll 5.1.2600.5507
C:\WINDOWS\system32\RPCRT4.dll 5.1.2600.6022
C:\WINDOWS\system32\rasadhlp.dll 5.1.2600.5512
C:\WINDOWS\system32\psapi.dll 5.1.2600.5512
C:\WINDOWS\system32\OLEAUT32.dll 5.1.2600.6058
C:\WINDOWS\system32\ole32.dll 5.1.2600.6168
C:\WINDOWS\system32\ntdll.dll 5.1.2600.6055
C:\WINDOWS\system32\NETAPI32.dll 5.1.2600.6260
C:\WINDOWS\system32\MSWSOCK.dll 5.1.2600.5625
C:\WINDOWS\system32\msvcrt.dll 7.0.2600.5512
C:\WINDOWS\system32\MSVCR100_CLR0400.dll 10.0.30319.1
C:\WINDOWS\system32\MSVBVM60.DLL 6.0.98.2
C:\WINDOWS\system32\msctfime.ime 5.1.2600.5512
C:\WINDOWS\system32\MSCTF.dll 5.1.2600.5512
C:\WINDOWS\system32\mscoree.dll 4.0.31106.0
C:\WINDOWS\system32\kernel32.dll 5.1.2600.5781
C:\WINDOWS\system32\iphlpapi.dll 5.1.2600.5512
C:\WINDOWS\system32\IMM32.DLL 5.1.2600.5512
C:\WINDOWS\system32\hnetcfg.dll 5.1.2600.5512
C:\WINDOWS\system32\GDI32.dll 5.1.2600.5698
C:\WINDOWS\system32\DNSAPI.dll 5.1.2600.6089
C:\WINDOWS\system32\dciman32.dll 5.1.2600.5512
C:\WINDOWS\system32\COMRes.dll 2001.12.4414.700
C:\WINDOWS\system32\comctl32.dll 5.82.2900.6028
C:\WINDOWS\system32\CLBCATQ.DLL 2001.12.4414.700
C:\WINDOWS\system32\ADVAPI32.dll 5.1.2600.5755
c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\nlssorting.dll 4.0.30319.296
c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\mscoreei.dll 4.0.30319.1
c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\diasymreader.dll 10.0.30319.1
c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\culture.dll 4.0.30319.1
c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\clrjit.dll 4.0.30319.269
c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\clr.dll 4.0.30319.296
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System\982a5b70d861cb34f85e041075d5112c\System.ni.dll 4.0.30319.296
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Xml\586e41e15e1d44fe197b9d1cc5575f8c\System.Xml.ni.dll 4.0.30319.1
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Windows.Forms\5e1418924e1f7b1cf13d9abf5deeffdd\System.Windows.Forms.ni.dll 4.0.30319.269
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Drawing\ec79f45debb2d466976d4e80b791b24d\System.Drawing.ni.dll 4.0.30319.1
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\System.Configuration\c409feb9182d01c80872f2031d68053e\System.Configuration.ni.dll 4.0.30319.1
C:\WINDOWS\assembly\NativeImages_v4.0.30319_32\mscorlib\16126cae96ea2422253ae06eeb672abc\mscorlib.ni.dll 4.0.30319.296
C:\Program Files\McAfee\SiteAdvisor Enterprise\saHook.dll 3.5.0.573
C:\Program Files\Encentuate\ObsBaseAgent.dll 8.1.0.130
C:\Program Files\Bonjour\mdnsNSP.dll 3.0.0.10
C:\IBM\InformationServer\Clients\Classic\vmdsrpsENU.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsrpos.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdspass.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsparENU.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsosvENU.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsobj.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsexpr.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsesvENU.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsedit.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\vmdsdirENU.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\dssingleton.dll 8.7.0.0
C:\IBM\InformationServer\Clients\Classic\director.exe 8.7.0.0
C:\IBM\InformationServer\ASBNode\apps\proxy\dotnet\xmogrt.dll 3.1.6.1
C:\IBM\InformationServer\ASBNode\apps\proxy\dotnet\MSVCR71.dll 7.10.3052.4
C:\IBM\InformationServer\ASBNode\apps\proxy\dotnet\MSVCP71.dll 7.10.3077.0
C:\IBM\InformationServer\ASBNode\apps\jre\bin\zip.dll 6.0.0.0
C:\IBM\InformationServer\ASBNode\apps\jre\bin\vmi.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\nio.dll 6.0.0.0
C:\IBM\InformationServer\ASBNode\apps\jre\bin\net.dll 6.0.0.0
C:\IBM\InformationServer\ASBNode\apps\jre\bin\jsig.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\jclscar_24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\java.dll 6.0.0.0
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9zlib24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9vrb24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9vm24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9vm\jvm.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9ute24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9trc24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\J9THR24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\J9PRT24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9jvmti24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9jit24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\J9HOOKABLE24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9gc24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9dyn24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9dmp24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\j9bcv24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\iverel24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\HYTHR.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\hyprtshim24.dll 2.4.1.10255
C:\IBM\InformationServer\ASBNode\apps\jre\bin\dbgwrapper.dll 6.0.0.0
C:\IBM\INFORM~1\Clients\Classic\DSRPC32.dll 8.7.0.1
C:\IBM\INFORM~1\Clients\Classic\DSOBJE~1.DLL 1.0.0.1
C:\IBM\INFORM~1\Clients\Classic\DSCLNT32.dll 1.0.0.1

Can that user's PC resolve the host name to an IP address (try it with PING from a CMD shell)? If not, edit the hosts file on that PC so that it can resolve the host name.

Ray

Yes, the users PC should be able to resolve the IP address

Below is the host entry i have on the users PC
111.666.777.88 hltixxx.abcc.ccc.com hltixxx

I tried ping on both the IP and server name, and had a successful reply.

Thanks
Srividya

make an entry as below (IP and HOST) and save it and then try
hltixxx.abcc.ccc.com seesm ok ; what is ? hltixxx

It seems host name

If the hostname of the services tier can be resolved, what about the hostname of the engine tier?

If these are the same, have you confirmed that all required services are running (server1 on the services tier, ASBNode and Logging agents and DataStage RPC daemon - at least - on the engine tier)?

Hi Ray

All the services on all the tiers are working. Everyone else from the team is able to connect to this server without any issues

The login issue from the client machine is not specific to a particular datastage server. This machine cannot connect to dev, sit, uat or prod using any login credentials.

The same credentials do work from every other system in the team.

We made sure the host names are set properly (copied host file from a connecting machine), pinged and used telnet to get successful response from the host machine, checked all the firewalls are set properly.

One question i had was, say the sever was down or not reachable for any reason, will i be getting the project details in the dropdown list? I was thinking the availability of projects indicates a successful connection to the server. Please correct me if i am wrong.

We have opened a ticket with IBM today, so i will post with the conclusion we reach

Thank you
Srividya

You would still get a list of projects, because that comes from the services tier. You may not be able to connect to a project because other services aren't running, but that would affect all users. Similarly, this particular user might not have rights in the project, but you tell us you're using credentials that work elsewhere, so it's not that. This one's a bit tricky - do let us know what Support come up with.

I am not sure about 8.7 but previous versions require .net framework 1.1
Did you verify if it is installed in the machine in question?

ok.. so IBM couldn't help much as they concur with us that the problem is with the system and not the server. as per them
the server identifies the project by ShortName/ProjectName
when i try "ping shortname", i dont get response from this single machine. Till we get a response for the short name the issue cannot be resolved.
Any suggestions on how to resolve this??

Thanks
srividya

Compare your DNS server addresses under TCP/IP setting between your working and non-working machine.

Go to your network and sharing center -- Click on Local or Wireless connection -- Properties -- (opens New window) Internet protocal version 6 (opens TCP/IPv6) -- properties -- (opens New window) Advanced -- (opens New window) DNS.

Do the same for TCP/IPv4 as well and see if there are any missing domain name between the machines; if any is missing you can add and try your connection.

This is a guess....

Srividya...can you pls tell me which policy caused the issue for you and how did you resolve it ?
Thanks