Community Discussions and Support
Pegasus hangs on start-up

[quote user="duncane"]Bump[/quote]

Try the Mercury support forum, you're very likely to meet more network savvy people there.

<p>[quote user="duncane"]Bump[/quote]</p><p>Try the <a href="/forums/9/ShowForum.aspx" mce_href="/forums/9/ShowForum.aspx" target="_blank">Mercury support forum</a>, you're very likely to meet more network savvy people there.</p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

We are running Pegasus 4.6 c/w Mercury on a Novell network. This works very well.

We use Citrix for remote access to the network with applications accessed via Citrix (including Pegasus) running on a Windows 2000 SP4 server. We have an intermittent problem when using this with Pegasus hanging on startup on the splashscreen, displaying the message "Locating Folders....0". Eventually we will get an error message saying insufficient memory and get dumped out of Pegasus (the server has 16Gb of RAM so isn't exactly low on memory). At this point all our network drives will have been disconnected as a result of the Pegasus crash. Our only solution is to reboot the Windows Server. Sometimes this is sufficient to allow us to log into Pegasus correctly, other times not. In the latter case, opening Pegasus on a Windows XP machine, closing it again may solve the problem. But again, not always. Does anyone have any ideas what might be happening?

 Many thanks for your help.

Duncan

<p>We are running Pegasus 4.6 c/w Mercury on a Novell network. This works very well.</p><p>We use Citrix for remote access to the network with applications accessed via Citrix (including Pegasus) running on a Windows 2000 SP4 server. We have an intermittent problem when using this with Pegasus hanging on startup on the splashscreen, displaying the message "Locating Folders....0". Eventually we will get an error message saying insufficient memory and get dumped out of Pegasus (the server has 16Gb of RAM so isn't exactly low on memory). At this point all our network drives will have been disconnected as a result of the Pegasus crash. Our only solution is to reboot the Windows Server. Sometimes this is sufficient to allow us to log into Pegasus correctly, other times not. In the latter case, opening Pegasus on a Windows XP machine, closing it again may solve the problem. But again, not always. Does anyone have any ideas what might be happening?</p><p> Many thanks for your help.</p><p>Duncan </p>

[quote user="duncane"]Does anyone have any ideas what might be happening?[/quote]

I don't know anything about Novell networks, but it might help if you provide any relevant version information and whether this happens on certain clients only (what makes the difference?) or on random ones.

<p>[quote user="duncane"]Does anyone have any ideas what might be happening?[/quote]</p><p>I don't know anything about Novell networks, but it might help if you provide any relevant version information and whether this happens on certain clients only (what makes the difference?) or on random ones.</p>
			Michael
--
IERenderer's Homepage
PGP Key ID (RSA 2048): 0xC45D831B
S/MIME Fingerprint: 94C6B471 0C623088 A5B27701 742B8666 3B7E657C

I am running Pegasus 4.61 on a Windows 2000 SP4 server with Novell Client 4.83 on a Novell 5.5 network. We only have this problem on the Win2000 server which we access using Citrix ICA. We can always open Pegasus from PCs in the office which run Win XP.

I am running Pegasus 4.61 on a Windows 2000 SP4 server with Novell Client 4.83 on a Novell 5.5 network. We only have this problem on the Win2000 server which we access using Citrix ICA. We can always open Pegasus from PCs in the office which run Win XP.
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft