can you still send me the hostfile and the registry dump? (as zip file) Dirk.
Woodstone's office are closed from April 22nd until April 26th 2004. Don't forget to vote for Servers Alive in the annual Sunbelt Target Awards http://www.sunbelt-software.com/targetawards/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Saturday, April 24, 2004 6:44 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] "Run-time error '13': Type mismatch" I made the registry change, and all is fine now. 1600 was installed over 1599, and 1599 was installed over 1591. I never enabled encryption manually. Neither did SA load without my original hostfile at any time. All the original passwords in my hostfile worked without retyping any of them. Let me know if you need more info. Thanks, JV. -- Jim Vaughan FAX: 402-399-3533 Information Services / Telecommunications & Networking Central States Health & Life Co. of Omaha - http://www.cso.com "Dirk Bulinckx" <[EMAIL PROTECTED] u> To Sent by: <[EMAIL PROTECTED]> [EMAIL PROTECTED] cc stone.nu Subject RE: [SA-list] "Run-time error '13': 04/23/2004 11:16 Type mismatch" PM Please respond to [EMAIL PROTECTED] nu Looks like the error is due to the high encryption. IF the high enctryption is enabled without the hostfile being loaded, SA will convert the password that are within the setup to high encryption but those in the hostfile are not and this causes the error 13 when using the hostfile. The simple solution is: * disable high encryption (this can only be done via the registry!) (HKEY_LOCAL_MACHINE\SOFTWARE\DBU Consulting\Servers Alive\StartUp\UseHighEncryption with a value of 0) BUT you will have to retype all the password that are in the setup. Now the question is did you install the 1599/1600 OVER an existing installation? If so did you enable the high encryption manualy (without loading the file?) Or did you do a fresh install (on a system without a previous SA installed) and used the "old" hostfile? Dirk. Woodstone's office are closed from April 22nd until April 26th 2004. Don't forget to vote for Servers Alive in the annual Sunbelt Target Awards http://www.sunbelt-software.com/targetawards/ -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of David Wheeler Sent: Saturday, April 24, 2004 12:06 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] "Run-time error '13': Type mismatch" I had some problems with my SA hanging so I upgraded to 4.1.1600. I then encountered similar problems with HTTPS and Oracle Checks using 4.1.1600 with Run time 13 Errors. I then removed the microsoft patches. and downgraded to 1591. I then retyped the passwords for HTTPS. Both HTTPS and Oracle then seemed to be ok. It seems to be either the beta OR the beta SA+ms patches. Note: Condensed for brevity. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Friday, April 23, 2004 2:29 PM To: [EMAIL PROTECTED] Subject: [SA-list] "Run-time error '13': Type mismatch" When I was running Servers Alive 4.1.1591, I had several checks set up to check perfmon logical disk counters for free megabytes, but I constantly battled "element not found" errors. So I turned these checks off. Recently, I read on this list that the newest beta version (1599 at the time) resolved this "element not found" issue by checking disk space in a different way. However, when I upgraded to Servers Alive 4.1.1599, all of my perfmon checks began to fail, and any attempts to edit a perfmon check results in a "Run-time error '13': Type mismatch" message, after which Servers Alive crashes. I upgraded to beta 1600 today yet still see the same behavior. Any advice? I'd rather not recreate all of the perfmon checks if I don't have to. Thanks! -- Jim Vaughan FAX: 402-399-3533 Information Services / Telecommunications & Networking Central States Health & Life Co. of Omaha - http://www.cso.com --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive The information contained in this email message may contain confidential or legally privileged information and is intended solely for the use of the named recipient(s). No confidentiality or privilege is waived or lost by any transmission error. If the reader of this message is not the intended recipient, please immediately delete the e-mail and all copies of it from your system, destroy any hard copies of it and notify the sender either by telephone or return e-mail. Any direct or indirect use, disclosure, distribution, printing, or copying of any part of this message is prohibited. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of XOMA. --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive --- [This E-mail scanned for viruses by Declude Virus] To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
