Hi

i recently attempted to deploy a write back cube in as2K SP3a, over the
internet, using SSL and basic authentication.

It seems that while client apps detect that the cube is write-back enabled,
the "commit transaction" fails for some reason.

I know the user has write back capability, and that the cube works fine,
because this issue does not appear if the user authenticates with integrated
authentication.

firewall issues make intergrated auth an impossibility.

can someone verify that this result is to be expected - and if thereis
either a work around, patch, or plans to correct in SQL SERVER 2005.

thx
Avi