Infinite Loop while cube processing in SSAS 2005 SP2

Hi,

We build the cube, quite large one processing 4 million records of data daily. It was working fine in SSAS 2005 Service Pack 1. But recently Service Pack 2 for SSAS came out, in the releases notes it said SP2 solves some of the issues we had on the drillthrough. So, after applying SP2 on the production server, running on 32 bit Windows 2003 SP2, the ETL process is stuck. It stuck while processing the cube, on large dimension.

I was wondering whether microsoft released hotfix for this issue or anyone else had this problem.

I note again, that whole thing was working fine under SSAS 2005 SP1 environment, but i believe in SP2 there is some flaw that leads to infinite loop while processing the cube.

Regards,

Bakhodir Makhamadov

Hello,

Short after releasing sp2 they came out again with an update of SP2 !?

Recreate all your partitions and redesign de storage designs, maybe this will help too !?sql

Infinite Loop while cube processing in SSAS 2005 SP2

Hi,

We build the cube, quite large one processing 4 million records of data daily. It was working fine in SSAS 2005 Service Pack 1. But recently Service Pack 2 for SSAS came out, in the releases notes it said SP2 solves some of the issues we had on the drillthrough. So, after applying SP2 on the production server, running on 32 bit Windows 2003 SP2, the ETL process is stuck. It stuck while processing the cube, on large dimension.

I was wondering whether microsoft released hotfix for this issue or anyone else had this problem.

I note again, that whole thing was working fine under SSAS 2005 SP1 environment, but i believe in SP2 there is some flaw that leads to infinite loop while processing the cube.

Regards,

Bakhodir Makhamadov

Hello,

Short after releasing sp2 they came out again with an update of SP2 !? Recreate all your partitions and redesign de storage designs, maybe this will help too !?

Infameous 0x80070005 ERROR: Access denied

Hi, my name is Beatriz and I'm another victim of the 0x80070005 from
Hell. I'm running WBEMTEST from a PC to connect to another one with WXP
SP2 and even:

1. The firewall is down.
2. Applied the commands:
netsh firewall set service RemoteAdmin enable
netsh firewall add portopening protocol=tcp port=135 name=DCOM_TCP135
3. Did the workaround suggested in:
http://support.microsoft.com/kb/909444
4. Ran the workaround in: http://support.microsoft.com/kb/884573
5. Added the account I use to access by Wbemtest with to the Default
Lauch Permissions with Full Control.
6. Checked up the registry
:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\forceguest
were set to 0.

I keep not being able to connect, and receving 0x80070005, what I'm
missing?!?!?!?Are you looking for SQL Server Integration Services help?|||

Did you ever get a response or resolution to this?

Hopefully, your system isn't still DOA 7-8 months later.

We have exactly the same issue with a brand-new server running WinServer 2003x64 R2

Have installed/reinstalled the entire OS three times now. The solution I guess is to do yet another reinstall and then not install the rogue security patch but that would leave us vulnerable to whatever the security patch was trying to fix and who knows what future M/Soft update won't do something similar?

|||Are you having SSIS problems when trying to connect to the SSIS service via Management Studio?

http://www.ssistalk.com/2007/04/13/ssis-access-is-denied-when-connection-to-remote-ssis-service/

Infameous 0x80070005 ERROR: Access denied

Hi, my name is Beatriz and I'm another victim of the 0x80070005 from
Hell. I'm running WBEMTEST from a PC to connect to another one with WXP
SP2 and even:

1. The firewall is down.
2. Applied the commands:
netsh firewall set service RemoteAdmin enable
netsh firewall add portopening protocol=tcp port=135 name=DCOM_TCP135
3. Did the workaround suggested in:
http://support.microsoft.com/kb/909444
4. Ran the workaround in: http://support.microsoft.com/kb/884573
5. Added the account I use to access by Wbemtest with to the Default
Lauch Permissions with Full Control.
6. Checked up the registry
:HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\forceguest
were set to 0.

I keep not being able to connect, and receving 0x80070005, what I'm
missing?!?!?!?Are you looking for SQL Server Integration Services help?|||

Did you ever get a response or resolution to this?

Hopefully, your system isn't still DOA 7-8 months later.

We have exactly the same issue with a brand-new server running WinServer 2003x64 R2

Have installed/reinstalled the entire OS three times now. The solution I guess is to do yet another reinstall and then not install the rogue security patch but that would leave us vulnerable to whatever the security patch was trying to fix and who knows what future M/Soft update won't do something similar?

|||Are you having SSIS problems when trying to connect to the SSIS service via Management Studio?

http://www.ssistalk.com/2007/04/13/ssis-access-is-denied-when-connection-to-remote-ssis-service/