January 20, 2010 at 12:40 pm
We are experiencing issues with some of the cube connections. It seems that the server name or dsn is messed up with some of the pc's. I tried to ping the server name with no issues. We are not on Kerberos, the FQDN does not work. If I change the Data Source from server to IPaddress in the .odc it works fine. Seems like only Vista/Office2007 pc's.
Sample of connection string:
Provider=MSOLAP.3;Integrated Security=SSPI;Persist Security Info=True;Initial Catalog=Cube;Data Source=IPAdress;MDX Compatibility=1;Safety Options=2;MDX Missing Member Mode=Error
Resolution:
Changing the datasource name from DSN to IPAddress
Error Message:
the following system error occurred: the message or signature supplied for verification has been altered
Article:
( It’s not Kerberos related, The FQDN does not work)
--------------------------------------------------------------------------------
fsugeiger
January 20, 2010 at 1:30 pm
Definitely Vista machines not Win7? Saw a similar issue on Win7, where a security dll was being affected by (of all things) the Messenger Login Helper Service (or similar named beasty). Removed the service, everything worked again. Perhaps a Vista patch has made your Vista systems more like Win7?
Details of the Wwin7 issue --> from Akshai Merchandani on SSAS team.
There are two separate issues for Windows 7:
1. Connecting using Excel over HTTP. This should work, but you must be on Windows 7 RTM -- there was a bug in WinHttp which was fixed in RTM. If you're on the RC, then you will have a problem.
2. Connecting using Excel over TCP. There is a known issue with this, and the workaround here until a patch is available is to use Kerberos. This issue shows up an error about "workstation trust relationship" -- it is caused by a custom security module that is installed by the Windows Live Sign In Assistant (SIA), so another alternative is to uninstall that temporarily but it can cause the Office Live Addin to not work as expected.
However, the original error message about access denied would appear to be independent of these issues. You might want to re-install the MSOLAP90/MSOLAP100 OLE DB provider and try again -- also you should try using SSMS on the box to see if you can connect over HTTP to see if it is a connectivity issue or a provider issue.
Steve.
January 20, 2010 at 1:42 pm
Ends up being Kerberos after all. Win Server 2008/Sql 2008 uses Kerberos, connection from Vista/Office2007 is having an issue with the the hops.
Issue resolved with HotFix:
http://support.microsoft.com/default.aspx/kb/969083
additional notes:
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply