Horkay Blog
The postings on this site are my own and do not represent my Employer's positions, advice or strategies.
Wednesday, September 16, 2009

2000 Ford Windstar, no heat, thumping or clicking sound coming from behind the radio. 

This is caused by the blend door actuator breaking.  Repair is fairly simple, though small hands and band aids are needed for this job.  The blend door actuator is located directly behind the radio, but it will require removing the radio and the entire front dash that houses the HVAC controls.

The procedure is fairly simple.  The actuator costs about $35-50.  Ford Dealer wanted $200.00 for this job, it took me about 30 minutes.

The Windstar Dash.

Remove the Radio.  If you still have the original Ford Unit, than you will need the Ford Radio Removal tool, u-shaped thingy, disconnect antenna and wiring harness, set aside.


After the radio is out, remove all the nobs from the HVAC Controls (put somewhere safe).

The HVAC Controls and remaining part of the dash trim is held in by four bolts, two up, two down.  The top two are by the radio.  The bottom two are to the left and right of the cup holder (when it is full open).  Remove these bolts and the HVAC and Trim should remove as a unit.  Remove the wiring harness and set aside.

Now you should have a clear view inside the dash.

If you look carefully all the way in the back you will see it.


Disconnect the wiring harness to the actuator.  There are 4 bolts to the actuator.  Using your really small miniature hands, get in there and unbolt them, going slow and carefully holding on the bolts so they don't fall, you'll need them for re-assembly.

Also this is where you will need the band-aids.

Once unbolted.  Remove the Actuator.

Now just reverse the whole process.  Being careful not to loose the screws, over-tighten them, cut yourself, and do Remember to plug in the wiring harness to the actuator.

Easy !

Wednesday, September 16, 2009 8:53:05 AM (Central Standard Time, UTC-06:00) |  |  Windstar#
Saturday, September 12, 2009

I'm in the middle of an all-nighter for a SAN Migration.  Lots of down time, here's what I found worth reading:

The unspoken truth about managing geeks.

Understanding Service Level Agreements for Database Development.

Is SQL Server's latest security hole a real threat?

Very interesting syntax of the in-clause I didn't know existed:

SELECT * FROM person.contact

WHERE 'thomas' in(Firstname,LastName,LEFT(emailaddress,7))

From the I did not know this would work department

Big competitors spark Netezza’s partner-friendly strategy

Keeley Hazell looks hot while she's shilling for something.

Don't ask me how I'd go from Keeley to Jeremiah Johnson, but all nighters due that to you, than and i've never been normal, it's boring.

"where ya headed?"
"Same place you are Jeremiah, Hell, in the end."

Link to download sound track to the movie, Crow Corner., a long time ago I had it on LP, doubt I'd ever find it on cd or mp3, but all night'ers have a way of helping you find things.



Saturday, September 12, 2009 8:40:51 PM (Central Standard Time, UTC-06:00) |  | General Technology | SQL Server | Web_Blog#
Thursday, September 10, 2009

Recently we upgraded to a new version of HP SIM (systems insight manager), of course not testing it or letting the DBA's know.  Suddenly some things crash.  The new version of HP Sim provides a "richer discovery model"; oh it's rich!

Seems the new version performs some type of scan on the scsi bus, which causes our multi-path software (EMC Powerpath) to loose connectivity to the SAN, this causes the file system to "Panic", and all filesystems unmount.  Nice.

SIM is a hardware monitoring solution from HP for HP servers.  The server administration team loves it, the SQL DBA's don't mind it.  It of course uses SQL Server for a back-end database, so it helps keep us employed as well !  Basically SIM provides hardware inventory and monitoring of the servers.


Version:  Systems Insight Manager 5.3 with SP1 - Windows
Build version:  C. 

Using the Manual Discovery Task that ships with the product.

The issue was most notable with our clustered servers, especially Polyserve.  Below were the error messages:

I/O error in nodelist_get for filesystem on psv30: nlblocknr=10, blocknr=10, nlsize=8192, size=8192, count=16.
umount: unmounting filesystem from psv30.
Filesystem on psv30 has finished disabling itself, and has no more writes to drain.
A psv-bound subdevice (psv7 - 0x8001) has been removed from the system.
Filesystem on psv39 has suffered a critical I/O error, and will be disabled to protect filesystem integrity.
The device, \Device\Harddisk140\DR645, is not ready for access yet.
\Device\MPIODisk398 is currently in a degraded state. One or more paths have failed, though the process is now complete.

Work closely with your administrators and be careful of how these monitoring solutions will affect your production servers.

Thursday, September 10, 2009 11:05:55 AM (Central Standard Time, UTC-06:00) |  | General Technology | Polyserve | SQL Server#
Sunday, September 06, 2009

Kansas City Natural Wheat

  • 6 lbs.  Weyermann Pale Wheat
  • 5 lbs.  German Pilsen
  • 1 Oz. Perle leaf hops, 7.9 AAU, bittering, 1 hour
  • 1 Oz. Saaz leaf hops, 6.7 AAU, 30 minutes
  • 1 Oz. Styrian pellets, 1.9 AAU, 15 minutes
  • Wyeast Weihenstephan Weizen 3068

Mash schedule

  • 153 degrees F for 60 minutes
  • 170 degress F for 10 minutes

Ferment, Rack onto secondary with 1 pound belgian white candi sugar, or 1 pound corn sugar, dextrose, complete fermenation, prime and bottle.

Sunday, September 06, 2009 8:34:12 AM (Central Standard Time, UTC-06:00) |  |  Beer #
Wednesday, September 02, 2009

There are many emphases for the SQL DBA, one of the major items is security.  Where I work security and patching have taken on new importance over the past 12 months.  Patching which used to be a yearly event, is now monthly or even weekly.  Combine that with SOX Controls and other internal controls, there is a focus on security.  Part of that is seen in SQL Server from Microsoft, kudos! 

The product gained a new level of security with SQL Server 2005.  Service Pack 2 gave us Login Triggers / Service Broker Events.  SQL 2008 saw the Builtin\Administrators account gone (separation of duties) and even more controls.

Than today it was distressing to see a news report about Microsoft ignoring a vulnerability with SQL Server, basically dismissing it as anyone with administrator privileges already has control [What happenned to separation of duties?].  The whole point of where security with SQL Server was going was to ensure that administrators could be properly segmented.  Where I work they'd like to get to the point where a SQL DBA can't even view or query the data that they administer.

If you find the below security vulnerability to be an issue than complain to Microsoft.  Also if you didn't know about this vulnerability, than you need to ensure to plug-in to some other industry news sources to get your information on vulnerability and patches, as you can't always count on Microsoft to disclose issues.

-----Original Message-----
From: Security Wire Daily [mailto:SearchSecurity@lists.techtarget.com]
Sent: Wednesday, September 02, 2009 10:38 AM
Subject: New SQL Server password flaw surfaces

SearchSecurity.com: Security Wire Daily
Breaking security news, the latest industry developments and trends
September 02, 2009

Michael S. Mimoso, Editor, Information Security magazine

Microsoft SQL Server administrators are being warned today about an
unpatched vulnerability in the popular database software that exposes
user passwords in the clear, as well as credentials delivered by
applications trying to access the database server.

Researchers at San Mateo, Calif.-based Sentrigo Inc., announced the
flaw this morning, and also revealed that Microsoft has no immediate
plans to release a patch for the vulnerability. Sentrigo, meanwhile,
said it has developed a free utility that will erase these passwords
from memory.
Read more:

Wednesday, September 02, 2009 12:19:21 PM (Central Standard Time, UTC-06:00) |  | SQL Server#
Popular Posts
Unpatched Vulnerabiltiy discovered ...
Spring Fornicator brewed...
SQL Agent will not start when a use...
SQL Instance will not fail back to ...
Hash Join vs. Merge Join
Recent Posts
May, 2019 (1)
April, 2019 (1)
March, 2019 (1)
February, 2019 (1)
January, 2019 (1)
December, 2018 (1)
November, 2018 (3)
October, 2018 (1)
June, 2018 (1)
May, 2018 (3)
April, 2018 (2)
February, 2018 (3)
January, 2018 (3)
November, 2017 (1)
October, 2017 (1)
August, 2017 (1)
June, 2017 (2)
May, 2017 (2)
April, 2017 (2)
March, 2017 (1)
February, 2017 (1)
December, 2016 (2)
October, 2016 (2)
September, 2016 (1)
August, 2016 (1)
July, 2016 (1)
March, 2016 (2)
February, 2016 (3)
December, 2015 (4)
November, 2015 (6)
September, 2015 (1)
August, 2015 (2)
July, 2015 (1)
March, 2015 (2)
January, 2015 (1)
December, 2014 (3)
November, 2014 (1)
July, 2014 (2)
June, 2014 (2)
May, 2014 (3)
April, 2014 (3)
March, 2014 (1)
December, 2013 (1)
October, 2013 (1)
August, 2013 (1)
July, 2013 (1)
June, 2013 (2)
May, 2013 (1)
March, 2013 (3)
February, 2013 (3)
January, 2013 (1)
December, 2012 (3)
November, 2012 (1)
October, 2012 (1)
September, 2012 (1)
August, 2012 (1)
July, 2012 (4)
June, 2012 (3)
April, 2012 (1)
March, 2012 (3)
February, 2012 (3)
January, 2012 (4)
December, 2011 (3)
October, 2011 (2)
September, 2011 (2)
August, 2011 (8)
July, 2011 (4)
June, 2011 (3)
May, 2011 (3)
April, 2011 (1)
March, 2011 (2)
February, 2011 (3)
January, 2011 (1)
September, 2010 (1)
August, 2010 (2)
May, 2010 (2)
April, 2010 (3)
March, 2010 (1)
February, 2010 (4)
January, 2010 (1)
December, 2009 (3)
November, 2009 (2)
October, 2009 (2)
September, 2009 (5)
August, 2009 (4)
July, 2009 (8)
June, 2009 (2)
May, 2009 (3)
April, 2009 (9)
March, 2009 (6)
February, 2009 (3)
January, 2009 (8)
December, 2008 (8)
November, 2008 (4)
October, 2008 (14)
September, 2008 (10)
August, 2008 (7)
July, 2008 (7)
June, 2008 (11)
May, 2008 (14)
April, 2008 (12)
March, 2008 (17)
February, 2008 (10)
January, 2008 (13)
December, 2007 (7)
November, 2007 (8)
Admin Login
Sign In