April 3, 2008 at 7:10 am
We process AS 2005 cubes overnight (via SSIS tasks in a SQL Agent job) and have been running for almost a year with few problems. However, for the past 3 nights our biggest cube (and a couple of smaller cubes) have failed on the processing step with the following message in the Event Log:
Event Type:Error
Event Source:MSSQLServerOLAPService
Event Category:(256)
Event ID:22
Date:4/3/2008
Time:3:07:20 AM
User:N/A
Computer:BOSDW01
Description:
The description for Event ID ( 22 ) in Source ( MSSQLServerOLAPService ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: File system error: The following error occurred during a file operation: The process cannot access the file because it is being used by another process. . (\\?\F:\AnalysisServicesDataFiles\SRs.0.db\SRS FACT 7.0.dim\173.SRS FACT.kstore)..
We have set the AS service to restart automatically on failure. Sometimes the automatic restart works fine, other times it fails with the same error message as above. In the cases when the automated restart of AS works all I need to do to resolve the issue is to manually restart the SQL Agent processing job. When AS fails to restart on the automated restart I am unable to restart the AS service using the Services screen. Once I needed to reboot the server and then AS started up fine.
I thought it might be related to Anti Virus software running at the time the cube was being processed, but sometimes NAV isn't running at the time of the failure and I had our NAV person exclude the AS directory from virus scans.
Anybody have any ideas? Will the /AUXSOURCE parm tell me anything more about the error.
April 9, 2008 at 5:28 am
FYI - I turned out that the contention was caused by our operations group running nightly backups to tape. Too bad that the event log didn't mention who was using the files. This would have made debugging easier.
July 22, 2008 at 11:13 am
Can you explain littl bit clear on this? did you say due space crunch this error popped up?
July 22, 2008 at 12:09 pm
No, it was file contention. Our operations group was running nightly backups to tape. They had the file locked when AS was trying to update it.
July 22, 2008 at 2:19 pm
Thanks for the reply. Can you let me know which is that file and the location of the file AS tries to update?
July 23, 2008 at 5:52 am
They are the files that are created when you process a cube.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply