Does it matter what time of the day you start the script? We run Meditech Scripts daily in a virtual environment on VMWare and typically what happens with ours is the script will run for hours continuously and then the Meditech window seems to lose focus and times out and closes, which then causes the script to stop. Luckily this happens inside of excel scripts where we can track the record number that it stopped on.
-- Sean Brady, BSMIS Interoperability Analyst, Information Systems | Augusta Health P.O. Box 1000 | 78 Medical Center Drive | Fishersville, VA 22939 (540) 332-5572 Office | (540) 332-5501 Fax | www.augustahealth.com<http://www.augustahealth.com/> [Aug_Hlth_1_Small]Click Here to Log a Help Desk Request<http://helpdesk/hsweb> From: [email protected] [mailto:[email protected]] Sent: Thursday, October 03, 2013 1:09 PM To: [email protected] Subject: RE:[talkbws] #safe# Scripts Not Running I use DameWare. I went through the settings on the virtual and made a few more changes. It just strange that this is happening now, as prior to the virtual I had this running on a PC With the exact same settings and it ran just fine everyday.. I had a few errors here and there, But it was errors that could be fixed and prevented. Does anyone else experience issues with Meditech running on a virtual machine? I was forwarded an email from another department here In our office and they are having issues with Meditech running on their virtual machine as well. Jesus From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Thursday, October 03, 2013 9:48 AM To: [email protected]<mailto:[email protected]> Subject: RE:[talkbws] #safe# Scripts Not Running If you have tightVNC installed as a host/client on appropriate machines, you can connect to the virtual box and leave it logged in. Closing the vnc session won't log out or inactivate the logged in session. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Thursday, October 03, 2013 12:01 PM To: [email protected]<mailto:[email protected]> Subject: RE:[talkbws] #safe# Scripts Not Running In theory, a virtual machine is identical to a physical pc, so there's no need to do anything specific from physical to virtual. What you are describing sounds like the pc is in a non-interactive state. Accessing a PC using Remote Desktop then "leaving" is a classic way to putting the pc in a non-interactive state. Logging off too would do the same thing. I'd be looking at something along those lines. Thom C. Blackwell, VP Technical Services Boston Software Systems, Inc. Phone: 866.653.5105 x807 Mobile: 508.423.8463 Fax: 508.319.3015 www.bostonsoftwaresystems.com<http://www.bostonsoftwaresystems.com/> Healthcare Automation - Revolutionizing How You Work. The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message. From: [email protected]<mailto:[email protected]> [mailto:[email protected]] Sent: Thursday, October 03, 2013 11:25 AM To: Talk Subject: [talkbws] #safe# Scripts Not Running I recently moved my Workstation to a Virtual Machine and ever since the switch My scripts are starting to get hung up over night and nothing is completed in the morning. When I login to the virtual machine all my scripts are stuck on a certain screen in Boston. Should I be running them differently now that it is on a virtual machine? Any help would be great. Thank you, Jesus Lopez System/Financial Analyst SMU Department Dignity Health 3033 N. 3rd Avenue Phoenix, AZ 85013 602.307.2754 (O) [email protected]<mailto:[email protected]> Caution: This email is both proprietary and confidential, and not intended for transmission to or receipt by any unauthorized persons. If you believe that is has been received by you in error, do not read any attachments. Instead, kindly reply to the sender stating that you have received the message in error. Then destory it and any attachments. Thank you. --- To post a message to this list, send mail to: [email protected]<mailto:[email protected]> You are currently subscribed as: [email protected]<mailto:[email protected]> Unsubscribe in the customer center on our website: http://www.bostonsoftwaresystems.com/Customers/ListServe.aspx --- To post a message to this list, send mail to: [email protected]<mailto:[email protected]> You are currently subscribed as: [email protected]<mailto:[email protected]> Unsubscribe in the customer center on our website: http://www.bostonsoftwaresystems.com/Customers/ListServe.aspx --- To post a message to this list, send mail to: [email protected]<mailto:[email protected]> You are currently subscribed as: [email protected]<mailto:[email protected]> Unsubscribe in the customer center on our website: http://www.bostonsoftwaresystems.com/Customers/ListServe.aspx --- To post a message to this list, send mail to: [email protected]<mailto:[email protected]> You are currently subscribed as: [email protected]<mailto:[email protected]> Unsubscribe in the customer center on our website: http://www.bostonsoftwaresystems.com/Customers/ListServe.aspx --- To post a message to this list, send mail to: [email protected] You are currently subscribed as: [email protected] Unsubscribe in the customer center on our website: http://www.bostonsoftwaresystems.com/Customers/ListServe.aspx
<<inline: image001.jpg>>
