Unexpected fatal error when connecting via client app
-
I have a server with SQL Server sp3a, AS sp4 and several different cubes. Recently we have begun to experience continuous unexpected fatal errors where the OLAP service stops & then restarts itself while we are querying some of the cubes from a client application.
It can be when submitting a query or even just when selecting dimension members, but it has rendered two of our virtual cubes almost unusable.
Both of these are fully processed each day; we have other cubes that seem unaffected - these are updated by a refresh data each day.
All our dimensions are shared and are reprocessed each day.
I think it must be a corruption of the data files somehow; I could restore from the CAB file but as we archive the cubes each night could the problem already be in the archive?
The cubes are too large & complex to recreate manually unless it was the only option.
Does anyone have any suggestions?
Thank you
Rachel
-
Try to install PTSlite.exe on client.(from microsoft site)
P.S. by the way I suggest you install already of SQL SErvice Pack 4 For SQL Server.
You Can download it from here.
http://www.microsoft.com/technet/prodtechnol/sql/2000/downloads/default.mspx
-
Could you tell me what this would achieve? Sorry, i am unfamiliar with PTS.
We use a ProClarity client to connect to AS and they insist the problem is not connected to their product. I was able to reproduce the problem using both their client PC app and their server-based browser but not using the MDX sample app, so I am trying to prove it is!
-
PTS = Pivot Table Services, the underlying way that all tools communcate with AS2K (there is no way but via PTS, it was so good, they rem'd it from 2K5
).You really should (need!) to have the same PTS version on the clients as SP you've installed on the server. Typcially when you unpoack the AS SP it will generate a set of folders, looking in these you should find PTSFUll and PTSLite, these need to be installed on every client. Haven't looked at Proclairty for ages, but depending on their server/client interction, if it's only ever the server accessin gthe AS server, then theoretically, you'll only need the new PTS on this server. If proclarity server = AS server (i.e. is same machine) then the dll's will already be there (from installing the AS SP) so no need to put the PTS on.
The eror itself sounds a little like issue # 833342 (http://support.microsoft.com/kb/833342/EN-US/) FIX: The Analysis Services service may shut down and then restart when you run MDX queries on a remote computer
Which was supposedly fixed in AS SP4. You're sure that it has been SP'd? (I know, it's the first thing you check
).Steve.
-
re: the complexity of build etc, if you're concerned that your archives may be corrupt, you could try the DSO-XML tool (unsported from msft, thnks Dave Wickert!). It scripts the cube to XML file/s, which can then be re-applied. Basiclly is a metadata extract, so you'd still need to reproces the cubes but would save you building from scratch.
Steve.
-
Thanks Steve
I applied the AS SP4 myself, so quite sure!
I downloaded the utility & tried it on one cube; but when I tried to recreate it from the xml file I got the following error message:
Object reference not set to an instance of an object.
Any tips on how to spot where the problem is in the xml file?
Thanks
Rachel
-
I have a friend who encountered this also but he had a fix - I'll find out what it was and post it.
Steve.
-
That would be great, thank you!
-
Hi Rachel, Finally caught up with him. Unfortunately, not a lot to offer. Basically he told me that he received the same error if trying to update or replace an item in the catalog. The only way he avoided the error was to use the (modified) xml file to create a new catalog. This resulted in the same outcome as he required - changing a datasource name without rebuilding the entire model - but may not be what you're after.
HTH,
Steve.
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply