OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
SQL IIS
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

SQL IIS


  • To: NTBUGTRAQLISTSERV.NTBUGTRAQ.COM
  • Subject: SQL IIS
  • From: Ray Atkinson <dataWORLDACCESSNET.COM>
  • Date: Wed, 25 Mar 1998 20:35:36 -0800
  • Reply-To: Ray Atkinson <dataWORLDACCESSNET.COM>
  • Sender: Windows NT BugTraq Mailing List <NTBUGTRAQLISTSERV.NTBUGTRAQ.COM>

This is a multi-part message in MIME format.

------=_NextPart_000_0030_01BD582D.90B22AD0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I recently ran into an interesting problem.

One of our web servers (IIS4) would periodically shut down.  Rebooting =
the machine had no effect.=20

I checked the logs.  NTE-L was clean, IIS-L was clean, SQL-L was =
clean...

Then I tried opening a few pages:
Every page returned:

ASP 0015 ...Trappable error in external object...script cannot =
continue...

However, html pages would come up fine.

So, I did a right click on the asp.dll and clicked register.  Then =
rebooted the machine again.

Now the asp pages worked again.  Everything seemed fine.  Then my boss =
got back in town and as I was telling him about the hiccup, it went down =
again.

I find out he was hitting the new site we just put up while talking to =
me on the phone.  So I reregistered the asp.dll again and rebooted, this =
time with the "no-net" profile to prevent outside interference.  Then =
watched the server.  All of the pages would come up fine, until you hit =
the new search page in the new site.  Hitting that page would cause the =
asp.dll to unregister thus causing all asp processing to cease on the =
machine.  Still no events are written to any of the logs (Including the =
SQL logs).

As a last resort, I used ISQL_W to just do a select of all of the =
records in the db.  Discovered that one of the tables, for which there =
is an inner join in the search asp page that crashes the asp.dll, had an =
extra 680 records in it.  ISQL could see them and read them. =20

After dropping the "corrupted" table, transferring a backup from my Dev =
machine, then doing the reregister and reboot routine.  Everything =
worked great.  Apparently while transferring the table to the server =
last week, through a dial-up, the connection was dropped.  Now, SQL-EM =
reported "...connection lost-retry?...", and after a yes, it reported a =
successful transfer.

Microsoft has already been informed and are supposedly attempting to =
reproduce.

(Shouldn't be that hard, just start a transfer, let it get a ways into =
it, click cancel and then during the cancel procedure, turn off your =
machine...voila-corrupted table...)

Just FEI ...

Ray Atkinson
System Administrator
World Access Network
DataWorldAccessNet.Com


------=_NextPart_000_0030_01BD582D.90B22AD0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD W3 HTML//EN">
<HTML>
<HEAD>

<META content=3Dtext/html;charset=3Diso-8859-1 =
http-equiv=3DContent-Type>
<META content=3D'"MSHTML 4.72.2106.6"' name=3DGENERATOR>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#000000 size=3D2>I recently ran into an interesting=20
problem.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>One of our web servers (IIS4) would periodically =
shut=20
down.&nbsp; Rebooting the machine had no effect. </FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I checked the logs.&nbsp; NTE-L was clean, IIS-L was =
clean,=20
SQL-L was clean...</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Then I tried opening a few pages:</FONT></DIV>
<DIV><FONT size=3D2>Every page returned:</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>ASP 0015 ...Trappable error in =
external=20
object...script cannot continue...</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>However, html pages would come up=20
fine.</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>So, I did a right click on the asp.dll and clicked=20
register.&nbsp; Then rebooted the machine again.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Now the asp pages worked again.&nbsp; Everything =
seemed=20
fine.&nbsp; Then my boss got back in town and as I was telling him about =
the=20
hiccup, it went down again.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>I find out he was hitting the new site we just put =
up while=20
talking to me on the phone.&nbsp; So I reregistered the asp.dll again =
and=20
rebooted, this time with the &quot;no-net&quot; profile to prevent =
outside=20
interference.&nbsp; Then watched the server.&nbsp; All of the pages =
would come=20
up fine, until you hit the new search page in the new site.&nbsp; =
Hitting that=20
page would cause the asp.dll to unregister thus causing all asp =
processing to=20
cease on the machine.&nbsp; Still no events are written to any of the =
logs=20
(Including the SQL logs).</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>As a last resort, I used ISQL_W to just do a select =
of all of=20
the records in the db.&nbsp; Discovered that one of the tables, for =
which there=20
is an inner join in the search asp page that crashes the asp.dll, had an =
extra=20
680 records in it.&nbsp; ISQL could see them and read them.&nbsp; =
</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>After dropping the &quot;corrupted&quot; table, =
transferring a=20
backup from my Dev machine, then doing the reregister and reboot =
routine.&nbsp;=20
Everything worked great.&nbsp; Apparently while transferring the table =
to the=20
server last week, through a dial-up, the connection was dropped.&nbsp; =
Now,=20
SQL-EM reported &quot;...connection lost-retry?...&quot;, and after a =
yes, it=20
reported a successful transfer.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>Microsoft has already been informed and are =
supposedly=20
attempting to reproduce.</FONT></DIV>
<DIV><FONT size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT size=3D2>(Shouldn't be that hard, just start a transfer, let =
it get a=20
ways into it, click cancel and then during the cancel procedure, turn =
off your=20
machine...voila-corrupted table...)</FONT></DIV>
<DIV>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>Just FEI ...</FONT></DIV>
<DIV><FONT color=3D#000000 size=3D2></FONT>&nbsp;</DIV>
<DIV><FONT color=3D#000000 size=3D2>Ray Atkinson<BR>System =
Administrator<BR>World=20
Access Network<BR><A=20
href=3D"mailto:DataWorldAccessNet.Com">DataWorldAccessNet.Com</A><BR></=
FONT></DIV></BODY></HTML>

------=_NextPart_000_0030_01BD582D.90B22AD0--