Here is the scenario: SSRS report in DEV, issues query that spins up Memory big time on SSAS. MsmDSrv showing 1+ GBs Memory usage in Task Manager.
After the connection is terminated, SSAS Service gets cycled. At that point, can connect via SSMS from another server to this SSAS server.
However when connecting from local SSMS, receive this error: A connection cannot be made. Eusure that the servier is running (admodClient). An operation on a socket could not be performed because the system lacked sufficient buffer space
or becasue a queue was full 127.0.0.1:2383
I really tried to find root cause - network trace, tcpview, vmmap, cycle SSAS, cycle SQL (shouldn't be related, but hey..) - but to no avail. I'd love to be able to fix this without bouncing the server.
SQL version 10.0.2531 SP1 x64, Windows 2008 R2 Enterprise. Ideas? Booting server now, but would looooove to have a non-boot solution to this
View Complete Post