P
Pat Allan
Hi.
Hoping for some light to be shed on this issue we've been having, but
after searching extensively in newsgroups and google, can't say I'm
really expecting much - but feel free to surprise me
We've got an OWC 9 (it has to be version 9 due to our clients using
Office 2k) Pivot table on our web application, talking to Analysis
Server via a HTTP Connection string using msolap.asp.
And by and large, this works fine - in our office, from staff members
personal internet accounts at their homes. However, it does not work at
our client's office. They get the following error: "0x80004005: Cannot
connect to server http://www.domain.net/Path/to/msolap/" (yes, I've
changed the url deliberately).
Their security has added our site to their trusted list, and enabled
data across domains, so I'm sure they're not the issue. Also, they're a
big corporate, so getting specific changes to their network is
difficult.
Of course, that means I have no clues left to work with. I've looked at
the packets sent to and from the server - they seem to be somewhat
understandable - I can see the measure and dimension names being sent
to the client. Its been suggested to me that, if the measure values is
binary (as opposed to ascii) the client's firewall could block it (only
allow HTTP transfers as ascii) - tho I'm thinking this isn't the case,
after looking at the packets.
From a completely different perspective, I've ensured that the
permissions on the cube allows 'Everyone', and (since our site is an
ASP.NET site), web.config has authentication set to 'None'. There is no
User ID and Password in the connection string, tho - it works fine
everywhere but at our client's, so I'm assuming that's not the problem.
Just to make matters just slightly more annoying, we can't test it from
our office, so seeing if our changes have any effect is just that bit
more difficult.
That aside, if anyone has any suggestions at all, please, post away.
Thanks
Pat Allan
========================
Solutions Developer
Managed Business Outcomes
Melbourne, Australia
Hoping for some light to be shed on this issue we've been having, but
after searching extensively in newsgroups and google, can't say I'm
really expecting much - but feel free to surprise me
We've got an OWC 9 (it has to be version 9 due to our clients using
Office 2k) Pivot table on our web application, talking to Analysis
Server via a HTTP Connection string using msolap.asp.
And by and large, this works fine - in our office, from staff members
personal internet accounts at their homes. However, it does not work at
our client's office. They get the following error: "0x80004005: Cannot
connect to server http://www.domain.net/Path/to/msolap/" (yes, I've
changed the url deliberately).
Their security has added our site to their trusted list, and enabled
data across domains, so I'm sure they're not the issue. Also, they're a
big corporate, so getting specific changes to their network is
difficult.
Of course, that means I have no clues left to work with. I've looked at
the packets sent to and from the server - they seem to be somewhat
understandable - I can see the measure and dimension names being sent
to the client. Its been suggested to me that, if the measure values is
binary (as opposed to ascii) the client's firewall could block it (only
allow HTTP transfers as ascii) - tho I'm thinking this isn't the case,
after looking at the packets.
From a completely different perspective, I've ensured that the
permissions on the cube allows 'Everyone', and (since our site is an
ASP.NET site), web.config has authentication set to 'None'. There is no
User ID and Password in the connection string, tho - it works fine
everywhere but at our client's, so I'm assuming that's not the problem.
Just to make matters just slightly more annoying, we can't test it from
our office, so seeing if our changes have any effect is just that bit
more difficult.
That aside, if anyone has any suggestions at all, please, post away.
Thanks
Pat Allan
========================
Solutions Developer
Managed Business Outcomes
Melbourne, Australia