10/17/2003 NT26 and ASP pages

[mresell]

Wasn't it stated that sp6 did not have this problem? Just out of curiosity can you use vb w/ other databases,say xbase.
Miva is the only web language I worked w/ that used standard xbase databases. Unfortunately, working w/ it now because of development cost getting high due to it now being binary and the engine being expensive.(for many ,anyway) So don't use xbase anymore. Since I have started working w/ php I am looking at what db options are out there other than mysql,pssql,mssql.

[nelsonke]

Any new information. I received a call late this morning from a client who believes they were down for 20 minutes. While we were talking their site came up, I presume that means the server was rebooted. This an established client but new to our hosting service. If this is not resolved soon, I would think a new server needs to be installed with older softare.

[newmem]

Originally posted by nelsonke
Any new information. I received a call late this morning from a client who believes they were down for 20 minutes. While we were talking their site came up, I presume that means the server was rebooted. This an established client but new to our hosting service. If this is not resolved soon, I would think a new server needs to be installed with older softare.

Is that site hosted on nt26?

[nelsonke]

Is that site hosted on nt26?

Yes. I checked the Monitor stats this morning. The ASP report for NT26 it shows downtime for more than 35 minutes yesterday, and averaged 40 minutes a day for the weeek.

I would still like to hear an update from staff.

[newmem]

I don't think the problem is only in nt26, my site is on nt27 and none of the asp pages were opening, then after 5 minutes I was able to open them, and again they stopped and so on.

I have started another thread for this same problem.

[nelsonke]

Originally posted by newmem
I don't think the problem is only in nt26, my site is on nt27 and none of the asp pages were opening, then after 5 minutes I was able to open them, and again they stopped and so on.

I have started another thread for this same problem.

Yes, farther up in the thread it is mentioned that NT27 is also affected as it is also running Windows server 2003. In fact I just checked the stats at http://status.vortechhosting.com:8080/ and the ASP downtime for yesterday was over 86 minutes, and so far today exceeds 59 minutes.

This is

[electricfox]

Honestly, Brad, I'm for telling microsoft to piss off and wait to adopt software once it has come out of "beta". This is a ridiculous issue they have created for themselves, no doubt on purpose because they noticed that everyone was using free Access instead of their way too expensive ms-sql. That whole thing about Frontpage just stinks of their "change in plans".

So, why spend more and "upgrade" to beta software? If these new servers are down more often than the older w2k boxes, I say stick with the w2k boxes!

PS: And all you hard-core access programmers out there, please try php and mySQL. As of last month I wouldn't dare develop anything in php - now that's all I want to develop in. PHP is so much better than ASP! Now with this Access issue, it's much cheaper too!

[newmem]

Originally posted by electricfox
So, why spend more and "upgrade" to beta software? If these new servers are down more often than the older w2k boxes, I say stick with the w2k boxes!

I think (and hope) this problem will be solved when ODBC is removed on Nov 11 as per the new announcement. And as for Win2003 over Win2000, I think it has it's advantages like faster speed and better SQL connectivity and stability.

PS: And all you hard-core access programmers out there, please try php and mySQL. As of last month I wouldn't dare develop anything in php - now that's all I want to develop in. PHP is so much better than ASP! Now with this Access issue, it's much cheaper too!

You can still use Access, you just have to use a different connection string.

[electricfox]

Oh, I was confused. At the beginning of the discussion it seemed like JET was the culprit too!

[admin]

Well Jet is the issue but its jet with the access driver not jet with the OLEDB driver.. Trust me it took me like 4 times to even understand on the phone..

Jet's the issue but jet and access driver make it 10 times worse. It will not fully fix this issue but it will make the system more stable. They also said it could fix it as it did for one customer but other they have just seen it help more then fix..

[newmem]

I was hoping for a full recovery........if Jet is still gonig to cause problems then the ASP pages will keep going down?

Then my vote would go to downgrading to Win2000 till MS comes up with Win2004.

[Brangwyn]

The ODBC Driver actually connects to JET as its next layer which is probably where you got confused.

[jmbeach]

I doubt we'll be seeing any Win2004, especially considering the big push for Longhorn.

[admin]

newmem, it will do it in windows 2000 as well just not as often.

It's something we "should" do cluster wide. We should also push for mysql or mssql to be used and not access this would help keep the servers a little more stable but then you have all the bandwidth issues with sql servers.. It's kind of win lose..


BTW as for the bandwidth issues I have been thinking about setting up a 2nd network just for MSSQL, mySQL and pgsql where they would just use an inside network and not have to go over the network with other bandwidth.. Would speed it up, there is just the cost in the 2nd nic cards if needed and 2nd switchs in each rack..

[electricfox]

not have to go over the network with other bandwidth.. Would speed it up, there is just the cost in the 2nd nic cards if needed and 2nd switchs in each rack..

Maybe Santa will bring them?