Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MTS & SQL Server locked up.

Status
Not open for further replies.

mkuan

Programmer
Sep 19, 2001
69
0
0
CA
I'm desperately needing to find the answer for my problem.

I've a client app that's an ActiveX EXE (let's call it EXE). Another app (let's call it APP1) passes an id to my ActiveX EXE, and the ActiveX EXE would call an MTS component to fetch some data from the SQL Server (based on that id) and passes the data back to the ActiveX EXE. The EXE uses the data to populate a form and show it. Simple enough.

The ActiveX EXE is installed on workstations (> 50), but about 10 - 20 workstations uses it at almost the same time, but never all together). The EXE works fine for about 10 - 15 days, and one day for no apparent reason, when APP1 tried to call the EXE, all of the workstations' EXE would display a server busy dialog box (with "Switch To" and "Retry" buttons), and it just wouldn't go away. If I tried to open up MTS Explore on the server, I couldn't. It's wouldn't open up. SQL Server was also not responding (Enterprise Manager and ISQLW wouldn't run). I had to reboot the server. As soon as I rebooted the server, I could open up MTS Explorer. When I checked the status view of the component that the EXE calls, I could see "Objects", "Activated", and "In Call" columns all had "21" in them. They were not going away. I had to shut down the package to clear it. After I cleared it, my ActiveX EXE worked fine again. However, after 10 - 15 days, the same problem would happen again. This morning, we found out one of the hard drives (RAID) on the server was faulty because the firmware on it needs to be updated. I don't if that would have anything to do with my problem.

I have made sure (let 2 other developers checked) all objects in APP1, EXE and MTS component are all releasing their objects when the code exits. We figure because something might not be releasing when there's a failure, the problem arises.

I hope someone could help me. Thx.

Min.
 
This is very indicative of a memory leak somewhere. Make sure that you're correctly releasing the objects when no longer in use. Ensure that all obselete instantiated objects are released in your error handler events as well. That's one thing that often gets overlooked. Neil Konitzer, President
Freisoft
 
I have already made sure that all objects are released. In addition, I have "on error resume next" in my error handler so that if any error happens, it would proceed to a section of the code that would release ALL objects in used in the procedure.

I hope it's the faulty drive that's causing the problem. Or else, I don't know what to do, except get fired. :(


Min.
 
For anyone who's interested... the problem I experienced was bowled down to faulty hardware, specifically the harddrive. That's what causes the intermittendt "Switch To" and "Retry" problem.

Happy new year.

Min.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top