Connection to Analysis services from VB - very slow

Dear All,

I noticed a strange problem with one of my client's computers where in establishing a connection with Analysis services from VB takes 6 seconds, when the computer is not connected to network, but it takes only a fraction of a second when the computer is in networ. We use ADOMD to connect to Analysis server. Analysis services is installed in the local machine.

I ran dependency walker and found that the dll WS2_32.dll (winsock dll) is taking most of the time when establishing connection.

This issue is very important for us and it would be great, if someone could help me in this.

Thanks in advance,

Niyas

Have you tried to use aternative machine name when connecting locally?

Try connecting to your Analysis Server using "localhost" or "127.0.0.1"

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights

|||

Hi Edward,

Thanks for your reply. I did try connecting to Analysis services using localhost, but there is no difference in the performance. I also created a machine level account (not in any domain) and tried connecting to Analysis services. But still, it does not show any difference.

This problem occurs in our client's machine alone and not in my computer or in my colleagues computers.

Thanks,

Niyas

|||

This might be related to VB initialization. Try posting your question on VB forum.

http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=32&SiteID=1

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||

Hi Edward,

I doubt whether this could be VB initialization problem, because the same problem occurred, when I tried to create a connection string using a .udl file. When I set the machine name, login credentials (Windows NT),driver and when I tested the conenction, it took 6 seconds, when I'm not in network and fraction of a second when I'm in network.

Thanks,

Niyas.

|||

Good. This is not VB related.

This is looks to be a general network problem. Try and see if you can find solution to this situation in windows networking forum. I doubt this is related to Analysis Services. Looks like generic connectivity problem.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.