Sequencing Safari 3.1.1
I have been trying to get Safari 3.1.1 sequenced into Softgrid for a few weeks now but so far I haven't had any luck.
Everything seems to sequence fine up until you launch Safari for the first time while the sequencer is running. Safari will launch and work as expected but when you try to exit the application and continue it will just hang and never close out completely. If you just blindly sequence the app and never launch it during sequencing and publish it to the softgrid server, it will launch just fine on the client but just like before the Safari.exe will not exit. Has anyone else seen this issue? Is there something I am doing wrong? I see someone in the SoftridGuru forums reported the same issue but there were no responses.
Thanks
Fritz
Everything seems to sequence fine up until you launch Safari for the first time while the sequencer is running. Safari will launch and work as expected but when you try to exit the application and continue it will just hang and never close out completely. If you just blindly sequence the app and never launch it during sequencing and publish it to the softgrid server, it will launch just fine on the client but just like before the Safari.exe will not exit. Has anyone else seen this issue? Is there something I am doing wrong? I see someone in the SoftridGuru forums reported the same issue but there were no responses.
Thanks
Fritz
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Ment
16 years ago
Posted by:
Chipster
16 years ago
I have experienced the same thing. I posted a note on softgridguru a while back but never got any replies. I tried sequencer 4.1 and i think i tried 4.2 as well with the same results. it's not the terminate children that helps, i think it's truly an app issue. I would love to know if someone does try the terminate children if that helps. but the problem then is that it's a blind sequence with no customization.
When the app is hung up, either on the sequencer or on the client machine after the blind sequence, you can't kill it. you have to reboot to get the process to go away. :(
When the app is hung up, either on the sequencer or on the client machine after the blind sequence, you can't kill it. you have to reboot to get the process to go away. :(
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.