Showing posts with label opening. Show all posts
Showing posts with label opening. Show all posts

Sunday, March 11, 2012

Diagrams not visible in EM in Terminal Server

Hi,
I cannot see the content of diagrams when opening the Enterprise Manager in
a RemoteDesktop session on a Terminal Server. The page is simply empty. I can
however create new diagrams which remain visible after closing an re-opening.
They are again not visible if modified in the Enterprise Manager on another
machine not logged on to the Terminal Server.
Any ideas are appreciated.
TIA,
Norbert Meiss
I just tried the same thing, and the diagrams opened fine for me.
Simon Worth
"Norbert Meiss" <NorbertMeiss@.discussions.microsoft.com> wrote in message
news:220AFBB0-43D5-44D7-A429-AD2D8B140E60@.microsoft.com...
> Hi,
> I cannot see the content of diagrams when opening the Enterprise Manager
in
> a RemoteDesktop session on a Terminal Server. The page is simply empty. I
can
> however create new diagrams which remain visible after closing an
re-opening.
> They are again not visible if modified in the Enterprise Manager on
another
> machine not logged on to the Terminal Server.
> Any ideas are appreciated.
> TIA,
> Norbert Meiss

Diagrams not visible in EM in Terminal Server

Hi,
I cannot see the content of diagrams when opening the Enterprise Manager in
a RemoteDesktop session on a Terminal Server. The page is simply empty. I can
however create new diagrams which remain visible after closing an re-opening.
They are again not visible if modified in the Enterprise Manager on another
machine not logged on to the Terminal Server.
Any ideas are appreciated.
TIA,
Norbert MeissI just tried the same thing, and the diagrams opened fine for me.
--
Simon Worth
"Norbert Meiss" <NorbertMeiss@.discussions.microsoft.com> wrote in message
news:220AFBB0-43D5-44D7-A429-AD2D8B140E60@.microsoft.com...
> Hi,
> I cannot see the content of diagrams when opening the Enterprise Manager
in
> a RemoteDesktop session on a Terminal Server. The page is simply empty. I
can
> however create new diagrams which remain visible after closing an
re-opening.
> They are again not visible if modified in the Enterprise Manager on
another
> machine not logged on to the Terminal Server.
> Any ideas are appreciated.
> TIA,
> Norbert Meiss

Diagrams not visible in EM in Terminal Server

Hi,
I cannot see the content of diagrams when opening the Enterprise Manager in
a RemoteDesktop session on a Terminal Server. The page is simply empty. I ca
n
however create new diagrams which remain visible after closing an re-opening
.
They are again not visible if modified in the Enterprise Manager on another
machine not logged on to the Terminal Server.
Any ideas are appreciated.
TIA,
Norbert MeissI just tried the same thing, and the diagrams opened fine for me.
Simon Worth
"Norbert Meiss" <NorbertMeiss@.discussions.microsoft.com> wrote in message
news:220AFBB0-43D5-44D7-A429-AD2D8B140E60@.microsoft.com...
> Hi,
> I cannot see the content of diagrams when opening the Enterprise Manager
in
> a RemoteDesktop session on a Terminal Server. The page is simply empty. I
can
> however create new diagrams which remain visible after closing an
re-opening.
> They are again not visible if modified in the Enterprise Manager on
another
> machine not logged on to the Terminal Server.
> Any ideas are appreciated.
> TIA,
> Norbert Meiss

Wednesday, March 7, 2012

devenv.exe hangs up with alomost 100% cpu usage

For some reason my visual studio with SSIS project hangs up with almost 100% cpu usage sometimes immediately after opening the studio.

Any resolution?

Thanks

I'm having the same problem and it is driving me nuts! I do a lot of BI work and this has disrupted my project timelines significantly.

As best as I can tell. it seems to have start after applying a patch to the .NET framework 2.0. The patch is defined in the KB922770. I'm not sure if this is the culprit by itself or if there are others factors re-enforcing the problem.

Let me know if you come up with a resolution.

Thanks, Darryl

darryl_jewett@.msn.com

|||

We were able to reduce the occurrence of hangup by 90% with two settings... particulary with the first one.

1. Project property -> Configuration Manger - > Build = UNCHECK (This gets checked mysteriously even though we Uncheck and save in TFS - so we verify for this setting frequently when we open the project). If it is checked - all packages in the project are built/compiled irrespective of package you are working on and if there are 100's of packages - compiling all of them takes hell of time.

2. Tools->Options->Environment->AutoRecovery - Save autorecovery information... = UNCHECK. (I did this bz I saw in the status bar of VS the message: Saving autorecovery details.. when it gets stuck)

Hope it helps you as well (if above setting are not important to you ).

But the problem has not gone altogether.... it still hangs up once in a while.

Thanks