While registering sqlserver group I am getting the following
error message
"You must upgrade your SQL Enterprise Manager and SQL DMO (SQL-OLE) to SQL server (SQL DMO) to connect to server."
Can any one please guide me how to overcome this proble.
thanx regardsLook at Knowledge Base Article:
HOW TO: Administer Different Versions of SQL Server by Using SQL Server Enterprise Manager (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q225/5/45.asp&NoWebContent=1)sqlsql
Showing posts with label group. Show all posts
Showing posts with label group. Show all posts
Thursday, March 22, 2012
Monday, March 19, 2012
Connections
I've got a satellite group that acts as their own dba's on
a 7.0 server. They claim that they cannot kill certain
connections, i.e. they typed in kill and nothing
happened. I have seen that happen with web-based
connection pooling apps but not with a regular app that
they're working with.
Anyway, what I wanted to ask is: is the kill command the
only way to kill a connection besides the winner-take-all
methods of taking the database offline or stopping and
restarting services? Just wondering if there's some magic
bullet that I hadn't heard of.
Kill can only be used to terminate user processes (typically spid>50) that
is not executing an extended procedure. Perhaps, that's what they're seeing.
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> I've got a satellite group that acts as their own dba's on
> a 7.0 server. They claim that they cannot kill certain
> connections, i.e. they typed in kill and nothing
> happened. I have seen that happen with web-based
> connection pooling apps but not with a regular app that
> they're working with.
> Anyway, what I wanted to ask is: is the kill command the
> only way to kill a connection besides the winner-take-all
> methods of taking the database offline or stopping and
> restarting services? Just wondering if there's some magic
> bullet that I hadn't heard of.
|||Thx but from what they're saying, it was definitely a user
process.
>--Original Message--
>Kill can only be used to terminate user processes
(typically spid>50) that
>is not executing an extended procedure. Perhaps, that's
what they're seeing.
>
>"NTel" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
on[vbcol=seagreen]
the[vbcol=seagreen]
all[vbcol=seagreen]
magic
>
>.
>
|||Sometimes you get "ghost connections". There are some reasons this can happen, the connection
executing an extended stored procedure is one such possibility. There can be other things as well,
but this has been getting better with versions and service packs.
Note that the connection might be in the middle of a large rollback, and it will not die until the
rollback is done.
No magic bullets here. Wait for a possible rollback to complete, if you feel certain you have waited
long enough, recycling the SQL Server is the way to go.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3c8901c48fae$fcf54370$a301280a@.phx.gbl...[vbcol=seagreen]
> Thx but from what they're saying, it was definitely a user
> process.
> (typically spid>50) that
> what they're seeing.
> message
> on
> the
> all
> magic
a 7.0 server. They claim that they cannot kill certain
connections, i.e. they typed in kill and nothing
happened. I have seen that happen with web-based
connection pooling apps but not with a regular app that
they're working with.
Anyway, what I wanted to ask is: is the kill command the
only way to kill a connection besides the winner-take-all
methods of taking the database offline or stopping and
restarting services? Just wondering if there's some magic
bullet that I hadn't heard of.
Kill can only be used to terminate user processes (typically spid>50) that
is not executing an extended procedure. Perhaps, that's what they're seeing.
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> I've got a satellite group that acts as their own dba's on
> a 7.0 server. They claim that they cannot kill certain
> connections, i.e. they typed in kill and nothing
> happened. I have seen that happen with web-based
> connection pooling apps but not with a regular app that
> they're working with.
> Anyway, what I wanted to ask is: is the kill command the
> only way to kill a connection besides the winner-take-all
> methods of taking the database offline or stopping and
> restarting services? Just wondering if there's some magic
> bullet that I hadn't heard of.
|||Thx but from what they're saying, it was definitely a user
process.
>--Original Message--
>Kill can only be used to terminate user processes
(typically spid>50) that
>is not executing an extended procedure. Perhaps, that's
what they're seeing.
>
>"NTel" <anonymous@.discussions.microsoft.com> wrote in
message[vbcol=seagreen]
>news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
on[vbcol=seagreen]
the[vbcol=seagreen]
all[vbcol=seagreen]
magic
>
>.
>
|||Sometimes you get "ghost connections". There are some reasons this can happen, the connection
executing an extended stored procedure is one such possibility. There can be other things as well,
but this has been getting better with versions and service packs.
Note that the connection might be in the middle of a large rollback, and it will not die until the
rollback is done.
No magic bullets here. Wait for a possible rollback to complete, if you feel certain you have waited
long enough, recycling the SQL Server is the way to go.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3c8901c48fae$fcf54370$a301280a@.phx.gbl...[vbcol=seagreen]
> Thx but from what they're saying, it was definitely a user
> process.
> (typically spid>50) that
> what they're seeing.
> message
> on
> the
> all
> magic
Connections
I've got a satellite group that acts as their own dba's on
a 7.0 server. They claim that they cannot kill certain
connections, i.e. they typed in kill and nothing
happened. I have seen that happen with web-based
connection pooling apps but not with a regular app that
they're working with.
Anyway, what I wanted to ask is: is the kill command the
only way to kill a connection besides the winner-take-all
methods of taking the database offline or stopping and
restarting services? Just wondering if there's some magic
bullet that I hadn't heard of.Kill can only be used to terminate user processes (typically spid>50) that
is not executing an extended procedure. Perhaps, that's what they're seeing.
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> I've got a satellite group that acts as their own dba's on
> a 7.0 server. They claim that they cannot kill certain
> connections, i.e. they typed in kill and nothing
> happened. I have seen that happen with web-based
> connection pooling apps but not with a regular app that
> they're working with.
> Anyway, what I wanted to ask is: is the kill command the
> only way to kill a connection besides the winner-take-all
> methods of taking the database offline or stopping and
> restarting services? Just wondering if there's some magic
> bullet that I hadn't heard of.|||Thx but from what they're saying, it was definitely a user
process.
>--Original Message--
>Kill can only be used to terminate user processes
(typically spid>50) that
>is not executing an extended procedure. Perhaps, that's
what they're seeing.
>
>"NTel" <anonymous@.discussions.microsoft.com> wrote in
message
>news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
on[vbcol=seagreen]
the[vbcol=seagreen]
all[vbcol=seagreen]
magic[vbcol=seagreen]
>
>.
>|||Sometimes you get "ghost connections". There are some reasons this can happe
n, the connection
executing an extended stored procedure is one such possibility. There can be
other things as well,
but this has been getting better with versions and service packs.
Note that the connection might be in the middle of a large rollback, and it
will not die until the
rollback is done.
No magic bullets here. Wait for a possible rollback to complete, if you feel
certain you have waited
long enough, recycling the SQL Server is the way to go.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3c8901c48fae$fcf54370$a301280a@.phx.gbl...[vbcol=seagreen]
> Thx but from what they're saying, it was definitely a user
> process.
>
> (typically spid>50) that
> what they're seeing.
> message
> on
> the
> all
> magic
a 7.0 server. They claim that they cannot kill certain
connections, i.e. they typed in kill and nothing
happened. I have seen that happen with web-based
connection pooling apps but not with a regular app that
they're working with.
Anyway, what I wanted to ask is: is the kill command the
only way to kill a connection besides the winner-take-all
methods of taking the database offline or stopping and
restarting services? Just wondering if there's some magic
bullet that I hadn't heard of.Kill can only be used to terminate user processes (typically spid>50) that
is not executing an extended procedure. Perhaps, that's what they're seeing.
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> I've got a satellite group that acts as their own dba's on
> a 7.0 server. They claim that they cannot kill certain
> connections, i.e. they typed in kill and nothing
> happened. I have seen that happen with web-based
> connection pooling apps but not with a regular app that
> they're working with.
> Anyway, what I wanted to ask is: is the kill command the
> only way to kill a connection besides the winner-take-all
> methods of taking the database offline or stopping and
> restarting services? Just wondering if there's some magic
> bullet that I hadn't heard of.|||Thx but from what they're saying, it was definitely a user
process.
>--Original Message--
>Kill can only be used to terminate user processes
(typically spid>50) that
>is not executing an extended procedure. Perhaps, that's
what they're seeing.
>
>"NTel" <anonymous@.discussions.microsoft.com> wrote in
message
>news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
on[vbcol=seagreen]
the[vbcol=seagreen]
all[vbcol=seagreen]
magic[vbcol=seagreen]
>
>.
>|||Sometimes you get "ghost connections". There are some reasons this can happe
n, the connection
executing an extended stored procedure is one such possibility. There can be
other things as well,
but this has been getting better with versions and service packs.
Note that the connection might be in the middle of a large rollback, and it
will not die until the
rollback is done.
No magic bullets here. Wait for a possible rollback to complete, if you feel
certain you have waited
long enough, recycling the SQL Server is the way to go.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3c8901c48fae$fcf54370$a301280a@.phx.gbl...[vbcol=seagreen]
> Thx but from what they're saying, it was definitely a user
> process.
>
> (typically spid>50) that
> what they're seeing.
> message
> on
> the
> all
> magic
Connections
I've got a satellite group that acts as their own dba's on
a 7.0 server. They claim that they cannot kill certain
connections, i.e. they typed in kill and nothing
happened. I have seen that happen with web-based
connection pooling apps but not with a regular app that
they're working with.
Anyway, what I wanted to ask is: is the kill command the
only way to kill a connection besides the winner-take-all
methods of taking the database offline or stopping and
restarting services? Just wondering if there's some magic
bullet that I hadn't heard of.Kill can only be used to terminate user processes (typically spid>50) that
is not executing an extended procedure. Perhaps, that's what they're seeing.
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> I've got a satellite group that acts as their own dba's on
> a 7.0 server. They claim that they cannot kill certain
> connections, i.e. they typed in kill and nothing
> happened. I have seen that happen with web-based
> connection pooling apps but not with a regular app that
> they're working with.
> Anyway, what I wanted to ask is: is the kill command the
> only way to kill a connection besides the winner-take-all
> methods of taking the database offline or stopping and
> restarting services? Just wondering if there's some magic
> bullet that I hadn't heard of.|||Thx but from what they're saying, it was definitely a user
process.
>--Original Message--
>Kill can only be used to terminate user processes
(typically spid>50) that
>is not executing an extended procedure. Perhaps, that's
what they're seeing.
>
>"NTel" <anonymous@.discussions.microsoft.com> wrote in
message
>news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
>> I've got a satellite group that acts as their own dba's
on
>> a 7.0 server. They claim that they cannot kill certain
>> connections, i.e. they typed in kill and nothing
>> happened. I have seen that happen with web-based
>> connection pooling apps but not with a regular app that
>> they're working with.
>> Anyway, what I wanted to ask is: is the kill command
the
>> only way to kill a connection besides the winner-take-
all
>> methods of taking the database offline or stopping and
>> restarting services? Just wondering if there's some
magic
>> bullet that I hadn't heard of.
>
>.
>|||Sometimes you get "ghost connections". There are some reasons this can happen, the connection
executing an extended stored procedure is one such possibility. There can be other things as well,
but this has been getting better with versions and service packs.
Note that the connection might be in the middle of a large rollback, and it will not die until the
rollback is done.
No magic bullets here. Wait for a possible rollback to complete, if you feel certain you have waited
long enough, recycling the SQL Server is the way to go.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3c8901c48fae$fcf54370$a301280a@.phx.gbl...
> Thx but from what they're saying, it was definitely a user
> process.
> >--Original Message--
> >Kill can only be used to terminate user processes
> (typically spid>50) that
> >is not executing an extended procedure. Perhaps, that's
> what they're seeing.
> >
> >
> >"NTel" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> >> I've got a satellite group that acts as their own dba's
> on
> >> a 7.0 server. They claim that they cannot kill certain
> >> connections, i.e. they typed in kill and nothing
> >> happened. I have seen that happen with web-based
> >> connection pooling apps but not with a regular app that
> >> they're working with.
> >>
> >> Anyway, what I wanted to ask is: is the kill command
> the
> >> only way to kill a connection besides the winner-take-
> all
> >> methods of taking the database offline or stopping and
> >> restarting services? Just wondering if there's some
> magic
> >> bullet that I hadn't heard of.
> >
> >
> >.
> >
a 7.0 server. They claim that they cannot kill certain
connections, i.e. they typed in kill and nothing
happened. I have seen that happen with web-based
connection pooling apps but not with a regular app that
they're working with.
Anyway, what I wanted to ask is: is the kill command the
only way to kill a connection besides the winner-take-all
methods of taking the database offline or stopping and
restarting services? Just wondering if there's some magic
bullet that I hadn't heard of.Kill can only be used to terminate user processes (typically spid>50) that
is not executing an extended procedure. Perhaps, that's what they're seeing.
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> I've got a satellite group that acts as their own dba's on
> a 7.0 server. They claim that they cannot kill certain
> connections, i.e. they typed in kill and nothing
> happened. I have seen that happen with web-based
> connection pooling apps but not with a regular app that
> they're working with.
> Anyway, what I wanted to ask is: is the kill command the
> only way to kill a connection besides the winner-take-all
> methods of taking the database offline or stopping and
> restarting services? Just wondering if there's some magic
> bullet that I hadn't heard of.|||Thx but from what they're saying, it was definitely a user
process.
>--Original Message--
>Kill can only be used to terminate user processes
(typically spid>50) that
>is not executing an extended procedure. Perhaps, that's
what they're seeing.
>
>"NTel" <anonymous@.discussions.microsoft.com> wrote in
message
>news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
>> I've got a satellite group that acts as their own dba's
on
>> a 7.0 server. They claim that they cannot kill certain
>> connections, i.e. they typed in kill and nothing
>> happened. I have seen that happen with web-based
>> connection pooling apps but not with a regular app that
>> they're working with.
>> Anyway, what I wanted to ask is: is the kill command
the
>> only way to kill a connection besides the winner-take-
all
>> methods of taking the database offline or stopping and
>> restarting services? Just wondering if there's some
magic
>> bullet that I hadn't heard of.
>
>.
>|||Sometimes you get "ghost connections". There are some reasons this can happen, the connection
executing an extended stored procedure is one such possibility. There can be other things as well,
but this has been getting better with versions and service packs.
Note that the connection might be in the middle of a large rollback, and it will not die until the
rollback is done.
No magic bullets here. Wait for a possible rollback to complete, if you feel certain you have waited
long enough, recycling the SQL Server is the way to go.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"NTel" <anonymous@.discussions.microsoft.com> wrote in message
news:3c8901c48fae$fcf54370$a301280a@.phx.gbl...
> Thx but from what they're saying, it was definitely a user
> process.
> >--Original Message--
> >Kill can only be used to terminate user processes
> (typically spid>50) that
> >is not executing an extended procedure. Perhaps, that's
> what they're seeing.
> >
> >
> >"NTel" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:3bb101c48fa2$07107710$a601280a@.phx.gbl...
> >> I've got a satellite group that acts as their own dba's
> on
> >> a 7.0 server. They claim that they cannot kill certain
> >> connections, i.e. they typed in kill and nothing
> >> happened. I have seen that happen with web-based
> >> connection pooling apps but not with a regular app that
> >> they're working with.
> >>
> >> Anyway, what I wanted to ask is: is the kill command
> the
> >> only way to kill a connection besides the winner-take-
> all
> >> methods of taking the database offline or stopping and
> >> restarting services? Just wondering if there's some
> magic
> >> bullet that I hadn't heard of.
> >
> >
> >.
> >
Wednesday, March 7, 2012
connection to cluster admin
I was trying to move the msdtc resource to the msdtc group and I have messed
up the cluster by taking too much offline in an attempt to move it. now I
don't have access to the cluster as the cluster ip, network name are
offline.
Can I tweak the registry somehow to regain access to it?
Stupid Stupid error.
Start Cluster Admin, but instead of using the cluster name, open it with a
period. Then start the resources.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Wayne" <watkinson@.sd43.bc.ca> wrote in message
news:O7gBmC6VHHA.5092@.TK2MSFTNGP03.phx.gbl...
>I was trying to move the msdtc resource to the msdtc group and I have
>messed up the cluster by taking too much offline in an attempt to move it.
>now I don't have access to the cluster as the cluster ip, network name are
>offline.
> Can I tweak the registry somehow to regain access to it?
> Stupid Stupid error.
>
|||Thank you...I was sweating bullets for awhile!
Nice trick to remember...
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:%23iTaiN6VHHA.1200@.TK2MSFTNGP02.phx.gbl...
> Start Cluster Admin, but instead of using the cluster name, open it with a
> period. Then start the resources.
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Wayne" <watkinson@.sd43.bc.ca> wrote in message
> news:O7gBmC6VHHA.5092@.TK2MSFTNGP03.phx.gbl...
>
up the cluster by taking too much offline in an attempt to move it. now I
don't have access to the cluster as the cluster ip, network name are
offline.
Can I tweak the registry somehow to regain access to it?
Stupid Stupid error.
Start Cluster Admin, but instead of using the cluster name, open it with a
period. Then start the resources.
Cheers,
Rodney R. Fournier
MVP - Windows Server - Clustering
http://www.nw-america.com - Clustering Website
http://msmvps.com/clustering - Blog
http://www.clusterhelp.com - Cluster Training
ClusterHelp.com is a Microsoft Certified Gold Partner
"Wayne" <watkinson@.sd43.bc.ca> wrote in message
news:O7gBmC6VHHA.5092@.TK2MSFTNGP03.phx.gbl...
>I was trying to move the msdtc resource to the msdtc group and I have
>messed up the cluster by taking too much offline in an attempt to move it.
>now I don't have access to the cluster as the cluster ip, network name are
>offline.
> Can I tweak the registry somehow to regain access to it?
> Stupid Stupid error.
>
|||Thank you...I was sweating bullets for awhile!
Nice trick to remember...
"Rodney R. Fournier [MVP]" <rod@.die.spam.die.nw-america.com> wrote in
message news:%23iTaiN6VHHA.1200@.TK2MSFTNGP02.phx.gbl...
> Start Cluster Admin, but instead of using the cluster name, open it with a
> period. Then start the resources.
> Cheers,
> Rodney R. Fournier
> MVP - Windows Server - Clustering
> http://www.nw-america.com - Clustering Website
> http://msmvps.com/clustering - Blog
> http://www.clusterhelp.com - Cluster Training
> ClusterHelp.com is a Microsoft Certified Gold Partner
>
> "Wayne" <watkinson@.sd43.bc.ca> wrote in message
> news:O7gBmC6VHHA.5092@.TK2MSFTNGP03.phx.gbl...
>
Connection Timeout when processing cube
I am getting a connection timeout error when processing a cube with measure group containing 4mil rows or so. It errors after 5 mins and after about 3mil rows have been read so it's probably not the ExternalCommandTimeout issue. The Fact table for the measure group is created using a named query. I would appreciate any insight into why the error is thrown after 5 mins. Here's part of the error:
===================================
The connection was lost. Close all processing dialog boxes and try processing the object again. (Microsoft Visual Studio)
===================================
The connection either timed out or was lost. (Microsoft.AnalysisServices)
Program Location:
at Microsoft.AnalysisServices.XmlaClient.EndRequest()
at Microsoft.AnalysisServices.XmlaClient.SendExecuteAndReadResponse(Boolean skipResults, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.Execute(String command)
at Microsoft.AnalysisServices.Server.Execute(String command)
at Microsoft.AnalysisServices.ManagementDialogs.OlapProcessProgressContainer.ProcessObjects()
===================================
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. (System)
Program Location:
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
at Microsoft.AnalysisServices.DimeRecord.ForceRead(Stream stream, Byte[] buffer, Int32 length)
at Microsoft.AnalysisServices.DimeRecord.ReadHeader()
at Microsoft.AnalysisServices.DimeRecord..ctor(Stream stream)
at Microsoft.AnalysisServices.DimeReader.ReadRecord()
at Microsoft.AnalysisServices.TcpStream.GetDataType()
===================================
An existing connection was forcibly closed by the remote host (System)
Dont think this has anything to do with ExternalCommandTimeout.
Try processing your cube using SQL Management Studio.
For that first deploy your project and in the project's properties in the deployment tab select Processing option = "Do Not Process".
Then open a SQL Management studio, connect to Analysis Services, navigate to your cube and try to process it. See if you get any errors.
Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Couplde of things:
Take a look at the msmdsrv.log located in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log folder.
Do you see there any messages around time you trying to process your cube.
If you havent yet, install SP1 of SQL Server and see if the same behavior persists.
Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Connection Timeout when processing cube
I am getting a connection timeout error when processing a cube with measure group containing 4mil rows or so. It errors after 5 mins and after about 3mil rows have been read so it's probably not the ExternalCommandTimeout issue. The Fact table for the measure group is created using a named query. I would appreciate any insight into why the error is thrown after 5 mins. Here's part of the error:
===================================
The connection was lost. Close all processing dialog boxes and try processing the object again. (Microsoft Visual Studio)
===================================
The connection either timed out or was lost. (Microsoft.AnalysisServices)
Program Location:
at Microsoft.AnalysisServices.XmlaClient.EndRequest()
at Microsoft.AnalysisServices.XmlaClient.SendExecuteAndReadResponse(Boolean skipResults, Boolean throwIfError)
at Microsoft.AnalysisServices.AnalysisServicesClient.Execute(String command)
at Microsoft.AnalysisServices.Server.Execute(String command)
at Microsoft.AnalysisServices.ManagementDialogs.OlapProcessProgressContainer.ProcessObjects()
===================================
Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. (System)
Program Location:
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.IO.BufferedStream.Read(Byte[] array, Int32 offset, Int32 count)
at Microsoft.AnalysisServices.DimeRecord.ForceRead(Stream stream, Byte[] buffer, Int32 length)
at Microsoft.AnalysisServices.DimeRecord.ReadHeader()
at Microsoft.AnalysisServices.DimeRecord..ctor(Stream stream)
at Microsoft.AnalysisServices.DimeReader.ReadRecord()
at Microsoft.AnalysisServices.TcpStream.GetDataType()
===================================
An existing connection was forcibly closed by the remote host (System)
Dont think this has anything to do with ExternalCommandTimeout.
Try processing your cube using SQL Management Studio.
For that first deploy your project and in the project's properties in the deployment tab select Processing option = "Do Not Process".
Then open a SQL Management studio, connect to Analysis Services, navigate to your cube and try to process it. See if you get any errors.
Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Couplde of things:
Take a look at the msmdsrv.log located in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\Log folder.
Do you see there any messages around time you trying to process your cube.
If you havent yet, install SP1 of SQL Server and see if the same behavior persists.
Edward Melomed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
Subscribe to:
Posts (Atom)