This project has moved and is read-only. For the latest updates, please go here.

The connection either timed out or was lost


This error seemed to crop up with we changed from the 2008 version of msmdpump.dll to the 2012 version. I can't verify as i can't get it to work period on either version. Is there a hardcoded url type that the addin is looking for or something? see the attached picture for the full error text.

file attachments


furmangg wrote Jan 27, 2014 at 11:26 PM

Can you post your connection string?

Can you please follow the instructions in the comments of this post regarding which checkboxes to check when you setup your connection?

dodom wrote Jan 28, 2014 at 10:21 PM

We are connecting to either a sql 2008 R2 std server or sql 2012 ent server. From the weblogs it looks like this: 2014-01-28 20:32:39 POST /olap/msmdpump.dll - 443 - ADOMD.NET - 401 2 5 0. Usually it is a 401 followed by a 200. So somehow doesn't pass the username/password

We are connecting with any of the following kinds of strings:

Provider=MSOLAP.4;Password=xxxxxxxxxxx;Persist Security Info=True;User ID=abc\efghij;Initial Catalog=cb_0010_SummaryCube;Data Source=;MDX Compatibility=1;Safety Options=2;MDX Missing Member Mode=Error;Subqueries=0

dodom wrote Jan 28, 2014 at 10:26 PM

Also, regarding how we set up our connections, we do all of the checks in that post, except we do not save the pwd in the file. This was working for us fine using the same methodology for setting up the connection before it stopped working.

furmangg wrote Jan 29, 2014 at 5:51 AM

If you save the password in the ODC file and have all the checkboxes checked, does OLAP PivotTable Extensions work? I'm afraid that from my research, the only way my add-in can properly capture the connection string with the password intact is if you follow that approach. (If you know another way through ADO or Excel APIs to capture the password you've typed in, I'm all ears.)

You are welcome to try installing older versions of the OLAP PivotTable Extensions add-in to see if they work better. For example, version 0.8.0 was the first to use the Analysis Services 2012 ADOMD.NET driver, so feel free to test prior versions by uninstalling the current version then installing an older version. I suspect it won't work, but feel free to try.

What security protocols do you have setup for that IIS website? Negotiate? Kerberos? Basic? Does it fail over http, too? (HTTPS is definitely a good thing, especially if you're doing basic auth, but it could certainly be the problem due to HTTPS certificates.)

I need to find some time to test this on my laptop to make sure it works for me. But I'm a bit swamped at the moment.

dodom wrote Jan 29, 2014 at 7:53 PM

I attempted to actually save the information in the .odc file and received the same error. As far as IIS we are using basic authentication.

I had one of our developers look at the source code. He just looked at the portion of the code that is used when you push the 'filter pivottable' button. He compiled it in .net 4 and it worked! He mentioned you were using .net 2, so he tried a couple of .net versions and 4 finally worked with that part. So, i'm assuming if you were to have a .net 4 version, maybe the problem would be solved. We must have something on our servers that we updated (recently as it worked before, and only for remote connections, local connections work fine), that is incompatible with .net 2.

is there any way you can compile a .net 4 version?


furmangg wrote Jan 29, 2014 at 8:37 PM

That's a very interesting finding! Thanks for the research.

Feel free to compile the OlapPivotTableExtensions.dll yourself as .NET4 and copy it over the existing DLL.

At this point, I'm not wild about upgrading to .NET4 because that will mean older computers can't use my add-in without installing new versions of .NET. But I will certainly consider it and do some further testing.

Can you be more specific about what specific lines of code or functions worked differently with .NET 4? Was it the impersonate section? Or was it a different section?

dodom wrote Jan 30, 2014 at 4:41 PM

The error occurs in the AdomdConnection.Open method. State = “_conn.Open();”