I've been getting an error in AS lately when restoring certain AS archives.
At first it was happening when I moved AS databases between work and home AS
instances, and thought it might be that I am running a later AS build (966)
at home. But now it even happens when trying a restore on the same work
server as where the archive was taken (build 760, SP3).



Restore goes normally until the final stage, where cube security is being
restored. The restore seems to stall, and then I get an OLAP Manger Addin
error with the text "Run-time error '-2147221387 (80040075)': Connection to
the server is lost." I have to shut down the MMC panel I was using to
access AS. When I bring it back up, the AS database may function partially,
but when you try to edit the cube that was having its security restored it
produces a string of Analysis Manager errors on their calculated members
"Calculated member 'xxxxx' creation failed. Not enough storage is available
to complete this operation."



I've had to trash the corrupt AS database and start over from a reliable
backup, manually reproducing all of the changes. This is not cool. The
first time it wasn't too bad, but this time I had created four new distinct
count cubes and a virtual cube to tie them together.

Has anyone seen this behaviour before?

Best regards, Mark

A critical data corruption error like that should handled by our support
folks.
We would consider the ability to not restore an archive to be a priority 1;
severity 1 problem; just a little bit down from the top category of "Server
Down".

If you have a Microsoft support contract, I would suggest that you contact
your TAM (Technical Account Manager) immediately and get this seriously
investigated. This is more than an informal discussion newsgroup can
typically address adequately.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mark Job" <markDOTjobATimmedientDOTcom> wrote

Thanks for the quick response Dave. We're an RSI and this is at a client
ISV site, so I'm sure we can come up with a support instance somewhere. As
the circumstances of the two instances of the problem were rather different,
I may wait to see another instance so that I can provide reliable recreation
info to support. I'll also keep both prior CAB files around.

On a related note, is there any word on when an SP4 might be available for
SS/AS 2000? There are 20 or so hotfixes out there, and it's been quite a
while since either SP3 or its Canadian cousin SP3a. One or two of the AS
fixes may be material to the app we are developing with this ISV, and life
would be a lot easier if we didn't have to tell their clients to apply a
hotfix to avoid critical errors...

Best regards, Mark

"Dave Wickert [MSFT]" <dwickert (AT) online (DOT) microsoft.com> wrote

SP4 is in-progress. Expect to see a beta out soon with RTM in the late
winter/springtime.
Besides the hotfix rollup, the biggest new feature will be support for AMD
64-bit running under WOW for all of the SQL Server 2000 components, i.e.
DTS, Analysis Services, etc. This will buy us an extra 1GB of virtual
memory -- not tremendous compared to what a native 64-bit support would give
(such as running natively under IA64), but for applications right on the 3GB
limit, it is very important.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI SystemsTeam
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Mark Job" <markDOTjobATimmedientDOTcom> wrote