What syntax are you using? This usually happens when you are trying to update an instance that does not exist if you are using the upgrade syntax ( setup /upgradesp ), or it can happen if you are using the install syntax ( setup /I ) and specifying an instance that already exists. You can have up to 16 instances of MSDE, if I am correct, and which one is created/upgraded depends on what sqlrunXX.msi file you use. If you are truly doing an install as you email suggests and have had failures during install, be sure to purge the registry of any references to the failed MSSQLSERVER (or it might show as just MSSQL) installation before trying again. But if this is an upgrade, do not remove anything from the registry, but you may want to look in the registry to ensure that you are using the correct instancename during the upgrade process (INSTANCENAME=<blahblah>).
Hope this helps. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Friday, July 18, 2003 3:02 AM To: [EMAIL PROTECTED] Subject: [ISSForum] updating MSDE I am trying to install MSDE SP3 on the System scanners MSDE. but i get the following error: "the instance name specified is invalid" Any clue? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, July 17, 2003 3:51 PM To: [EMAIL PROTECTED] Subject: RE: [ISSForum] Internet Scanner 7 - IP Spoofing Does this happen with Internet Scanner 6.2.1? -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 16, 2003 3:35 PM To: [EMAIL PROTECTED] Subject: [ISSForum] Internet Scanner 7 - IP Spoofing Sharing a lesson learned. Internet Scanner version 7 has a check for Stealth Port Scanning. The documentation states that the check spoofs an IP address, however what you don't know is something I found out the hard way. When the Stealth scan occurs it uses a Raw Packet Server that is designed to spoof the IP addresses. What happens is that the IP address of the system used to perform the scans is reversed. For example, the scanner's IP address is 205.30.112.25, it becomes 25.112.30.205 when it is spoofed, and this is the address used to perform a stealth port scan. The target system being probed responds to the spoofed IP address. Since this address is not part of our domain the response is routed to the Internet! Not a good idea! So now you are spewing responses from all the internal IP addresses out the internet to a spoofed address. It is conceivable that someone watching your domain could pick up on this behavior and learn what the IP address of your scanner is, plus collect IP address of all your internal systems. This may not be good idea if you have mission critical or classified systems that you were scanning for vulnerabilities. I think this is a breach of internal information that should not be happening, and that the user community needs to know about. Fortunately we monitor our outgoing traffic at the firewall and picked this up quickly. I confirmed this behavior with ISS and they responded that the check is performing as designed! However they would look into updating the documentation. You can confirm this by performing a scan and watching the firewall, then search the session log for Stealth and you will see what happens. Rick Berg Pacific Northwest National Laboratories _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo
