Wincf Problems

Customer Support Customer Only Discussion
1

Hi,

I visit my clients sites usualy two to three times a day to do routine updates and/or some quick checks on how they are doing and in the last three or so weeks, although it may just be my wierd luck, but nearly every time I’m at those sites on Wincf, there is some kind of issue happening; slow page load rates, timeouts, PHP and/or Coldfusion server lockups. I go to jodopulse.com to verify that there is indeed a problem.
(Assuming that the red indicates “server down”, just today Coldfusion was restarted five times between 15:30 and 18:00)

I have read the recent thread regarding a mail issue due to some spammer and the ODBC problem mentioned in another thread to help out the situation. As far as the ODBC issue, I use the ticket system to add a DNS everytime anyway, 24 hours is way to long to wait.

It’s really curious that the configuration on Win6 seems to run really well in comparison to the configuration on Wincf which, as I have read here, was meant to get away from the ASP/Coldfusion problems in order to increase server stability. I don’t have any sites on Win6, I’m just going by what I see when I check out the server status at jodopulse.com, and while there, I tend to compare the status of the two servers.

I’m guess what I’m really getting at is this, are the email and ODBC issues all that are keeping Wincf from running with the same stability that Win6 seems to have and to have consistantly decent +/- page load times?

Thanks (I feel better now),
Steve

smallgraph.jpg

2

manopb,

The issues with CF DSNs, is that if anyone uses the CF DSN creation from the Hsphere, it can cause the ODBC file to become corrupt. WinCF has been super stable until the last 3 weeks as you have noted, I am cracking down hard on some bad coding, and anyone that gets ane mail about it needs to follow up ASAP or risk site suspension.

3

I noticed a thread over at houseoffusion.com that may be of note:

"[I]Running on W2k3 SP1 Standard Server with CFMX running and accessing it via Terminal Services has had the annoying side effect of driving up the memory usage of winlogon.exe into the hundreds of MB…

by simply adding “/console” to the mstsc.exe command in the shortcut or invoking the TS client from a command prompt using “mstsc /console”.[/I] "

For the full thread:
http://www.houseoffusion.com/cf_lists/index.cfm/method=messages&threadid=43153&forumid=4#223366

This is not to say that I’ve been experiencing any real problems; actually things have been pretty smooth.

4

I have all the techs using the /console command for the most part these days :slight_smile:

It makes sure they see any console errors, it makes the session faster, and it keeps the terminal sessions fro being used.