Re: Date of executable
On 7/11/07, Jeff Johnson [EMAIL PROTECTED] wrote: Mike: I was using something like this, but I am not only working with terminal servers, but also virtual terminal servers. What's a virtual terminal server? Is that a session of the product formerly know as Terminal Server running in a VM? -- Ted Roche Ted Roche Associates, LLC http://www.tedroche.com ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
RE: Date of executable
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ted Roche Sent: Thursday, July 12, 2007 5:50 AM To: [EMAIL PROTECTED] Subject: Re: Date of executable On 7/11/07, Jeff Johnson [EMAIL PROTECTED] wrote: Mike: I was using something like this, but I am not only working with terminal servers, but also virtual terminal servers. What's a virtual terminal server? Is that a session of the product formerly know as Terminal Server running in a VM? -- Ted Roche Ted Roche Associates, LLC http://www.tedroche.com Ted: I'm sure what it is. The word associated with the setup is called virtualization. They are all terminal servers, but most are physical servers, but a couple of them are virtual servers. A virtual terminal server was brought on line with a very old and outdated version of the executable. When installing the executable on terminal services it dates the exe the date and time it is copied to the server and not the date and time the exe was built. The only way to find the culprit is to navigate to each terminal server and right click on the executable. It seems it would be easier for me to id the terminal server when something goes wrong. I can work around this going forward, but that doesn't help going back. Jeff Jeff Johnson [EMAIL PROTECTED] 623-582-0323 Fax 623-869-0675 --- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/x-pkcs7-signature --- ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
RE: Date of executable
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike yearwood Sent: Thursday, July 12, 2007 5:35 AM To: [EMAIL PROTECTED] Subject: RE: Date of executable Hi Jeff Does this help? lcExe = UPPER(JUSTFNAME(SYS(16, 0))) IF .EXE $ m.lcExe AGETFILEVERSION(laDetails, m.lcExe) ENDIF Mike: I was using something like this, but I am not only working with terminal servers, but also virtual terminal servers. We blew up a payroll file due to load balancing picking up a terminal server that was supposed to be offline that had an old version of the exe. When we spot a problem it would be better to know that the executable is out of date and then query which virtual machine we are running on. I would really like something like VERSION() for the exe coming from within the program. Does the exe running (in ram) get out of sync with the one on the drive? Wouldn't a virtual machine have a copy of the exe file to launch from? Mike: No, that doesn't happen. Please read my post to Ted. Thanks, Jeff Jeff Johnson [EMAIL PROTECTED] 623-582-0323 Fax 623-869-0675 --- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/x-pkcs7-signature --- ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
RE: Date of executable
Hi Jeff Ted: I'm sure what it is. The word associated with the setup is called virtualization. They are all terminal servers, but most are physical servers, but a couple of them are virtual servers. A virtual terminal server was brought on line with a very old and outdated version of the executable. When installing the executable on terminal services it dates the exe the date and time it is copied to the server and not the date and time the exe was built. The only way to find the culprit is to navigate to each terminal server and right click on the executable. It seems it would be easier for me to id the terminal server when something goes wrong. I can work around this going forward, but that doesn't help going back. Mike: No, that doesn't happen. Please read my post to Ted. Do you mean you want to find a way to ask each copy of the program in each virtual machine for the version? I don't have a clue how to go about doing that. Mike ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
RE: Date of executable
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike yearwood Sent: Thursday, July 12, 2007 7:46 AM To: [EMAIL PROTECTED] Subject: RE: Date of executable Hi Jeff Ted: I'm sure what it is. The word associated with the setup is called virtualization. They are all terminal servers, but most are physical servers, but a couple of them are virtual servers. A virtual terminal server was brought on line with a very old and outdated version of the executable. When installing the executable on terminal services it dates the exe the date and time it is copied to the server and not the date and time the exe was built. The only way to find the culprit is to navigate to each terminal server and right click on the executable. It seems it would be easier for me to id the terminal server when something goes wrong. I can work around this going forward, but that doesn't help going back. Mike: No, that doesn't happen. Please read my post to Ted. Do you mean you want to find a way to ask each copy of the program in each virtual machine for the version? I don't have a clue how to go about doing that. Mike Mike: That is what they asked me to do. Is there a way to check all of the terminal servers? Here is what I have decided to do: I have hooks in my application that have an external class that has a maintenance function. I found out that the executable will run from the V drive regardless of what server it is on. So I will do an AGETFILEVERSION(la, 'V:\MYAPP.EXE') and if it is not the one it is supposed to be, I will notify the user and close the application. Thanks for your help. Jeff Jeff Johnson [EMAIL PROTECTED] 623-582-0323 Fax 623-869-0675 --- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/x-pkcs7-signature --- ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Date of executable
Is there any way to get the date and version of the executable while running in production? FDATE() and AGETFILEVERSION() you have to pass the file name. This application is running on terminal servers and it would be better if we could get those two bits of information programmatically. Jeff Jeff Johnson [EMAIL PROTECTED] 623-582-0323 Fax 623-869-0675 --- StripMime Report -- processed MIME parts --- multipart/signed multipart/alternative text/plain (text body -- kept) text/html application/x-pkcs7-signature --- ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
Re: Date of executable
Hi Jeff Is there any way to get the date and version of the executable while running in production? FDATE() and AGETFILEVERSION() you have to pass the file name. This application is running on terminal servers and it would be better if we could get those two bits of information programmatically. Does this help? lcExe = UPPER(JUSTFNAME(SYS(16, 0))) IF .EXE $ m.lcExe AGETFILEVERSION(laDetails, m.lcExe) ENDIF ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
RE: Date of executable
-Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mike yearwood Sent: Wednesday, July 11, 2007 11:45 AM To: [EMAIL PROTECTED] Subject: Re: Date of executable Hi Jeff Is there any way to get the date and version of the executable while running in production? FDATE() and AGETFILEVERSION() you have to pass the file name. This application is running on terminal servers and it would be better if we could get those two bits of information programmatically. Does this help? lcExe = UPPER(JUSTFNAME(SYS(16, 0))) IF .EXE $ m.lcExe AGETFILEVERSION(laDetails, m.lcExe) ENDIF Mike: I was using something like this, but I am not only working with terminal servers, but also virtual terminal servers. We blew up a payroll file due to load balancing picking up a terminal server that was supposed to be offline that had an old version of the exe. When we spot a problem it would be better to know that the executable is out of date and then query which virtual machine we are running on. I would really like something like VERSION() for the exe coming from within the program. Jeff Jeff Johnson [EMAIL PROTECTED] 623-582-0323 Fax 623-869-0675 --- StripMime Report -- processed MIME parts --- multipart/signed text/plain (text body -- kept) application/x-pkcs7-signature --- ___ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
