Dreamweaver Crashes in Vista

In my particular situation, I'm working in Dreamweaver CS3 in Vista Enterprise (x64). Every time I opened DW, it would crash with no warning. The DW screen would get washed out and an error would come up telling me that DW crashed and vista was trying to figure out why. The explanation vista crash adviser gave was something related to MS kb937491, but after researching the reg keys this addresses, it was not the issue. Some additional research indicated that this was (yet another) problem with DW's use of a WinFileCachexxxx.dat file. See my previous post about the solution to this problem. Interestingly, this happened right after DST took affect and some of the things I researched indicated that this switch has a tendancy to corrupt the WinFile files.

Windows Update Page is Blank in IE on XP SP3

Here's a new one I've never seen until last week. Latest and greatest IE8, XP SP3 with all the trimmings (all fixes) and when you visit http://windowsupdate.microsoft.com - you get a blank (white) page that doesn't appear to load anything. If you view the source, you'll see that there's a whole page there telling you that either your browser doesn't support active x or it is not allowing active x content. Smooth move there MS, way to test your shit!

If you visit http://update.microsoft.com/ - the page loads, but you see an error message telling you:

"Files required to use Windows Update are no longer registered or installed on your computer. To continue:

Click option 1: Register or reinstall the files for me now (Recommended)
Click option 2: Let me read about more steps that might be required to solve the problem."

Clicking option 1 may fix the problem, but this is doubtful. Ignore option 2 as it does not contain ANY relevant information for fixing the problem. The problem is that for some reason, a bunch of the DLL's required by windows to run windows update have become unregistered. What you'll need to do:

1) Start -> Run -> cmd (to open a command window)
2) type: regsvr32 wuapi.dll [enter]
3) type: regsvr32 wups.dll [enter]
4) type: regsvr32 wuaueng.dll [enter]
5) type: regsvr32 wucltui.dll [enter]
6) type: regsvr32 atl.dll [enter]
7) type: regsvr32 msxml3.dll [enter]

After every time you hit enter, you should see a window that pops up and tells you that the DLL has been successfully registered. When you're done with registering the last DLL, go back to the updates page in IE and click on option 1 - let windows do its thing. When it's done, you should be able to visit either updates.microcrosoft.com or windowsupdate.microsoft.com without a problem.

And now, a big round of applause to MS for creating an error message page that their browser won't display. Good work fellas! Way to test and maintain your products. Helluva job... really!

Thunderbird Error: Dovecot/Postfix

"The current command did not succeed. The mail server responded: error"

This is the error that Thunderbird 2 [2.0.0.23] reported when I tried to check my email this morning. Did some digging and found that the problem is with the mbox format on the server. Some tweaking yesterday for mail server migration must have messed this one up. I tailed /var/log/maillog on the mail server and watched for errors. I saw:

File isn't in mbox format: /var/mail/username

Edited /var/spool/mail/username and got rid of 2 garbage lines at the top of the file. Restarted postfix and dovecot for good measure and fired Thunderbird back up. No more errors and it looks like all my email is there.

GoDaddy Domain and Hosting Transfer

I'm blogging about this as a warning to others. The scenario:

You have a client who is dissatisfied with their current web developer and wants you to take control of their domain, update their site and provide hosting for them. Lucky for them, their current developer has everything hosted at GoDaddy and you happen to have a hosting account at GoDaddy as well. As the techs will tell you on the phone or over email, "it's a very simple procedure and your customer will not experience any interruption of service". This is only partially true.

Now, the first thing you should do as a developer who isn't a shyster, always register your client's domains in their name. Make yourself any of the other contacts so that you can make changes as needed, but for the good of everyone, register the domain in their name. The client in question was new to the web and trusted his former developer to do the right thing and allowed them to register everything in the developer's name. Now that we want to transfer control, the developer decided to be difficult. No worries, the Hebrew Hammer never takes no for an answer and so began the "Domain Dispute" process with GoDaddy.

Step 1: Email 'domaindisputes@godaddy.com' - this gets the ball rolling.

Step 2: They will email you back and ask you to fill out a form on their website. In my case, the information I was entering did not match the whois info for the domain and no combination of what the whois information *should* have been worked. This required an email to domains@godaddy.com explaining to them the error I was getting when trying to complete the form. They replied back and gave me the option of sending them some form of ID that identified me as a legal representative of the "rightful owner" of the domain. This was done so in the form of my client's fictitious name registration with the state of Florida. Two days later I was in control of the domain.

Transfer of the domain, dns and email internally with GoDaddy was a breeze. No interruption of email to my client whatsoever, but the process of getting their hosting set up again has been an issue. The problem with GoDaddy is thus; if someone else (regardless of whether or not they control the domain) has the domain you want to host in THEIR hosting account manager, you *cannot* add it to YOUR hosting until they delete it. Well, we've already established that the previous developer was a scum-bag, so good luck getting them to delete the domain in a timely manner. Enter...

Step 3: Establish a 'Cease and Desist Order' through GoDaddy. If you've gone through the whole domain transfer process and the individual formerly in control of hosting (through GoDaddy) won't remove the domain, you can ask GoDaddy to initiate a "Cease and Desist Order" which basically gives the former controlling party 72 hours to comply with the order before GoDaddy forces the deletion of the domain from THEIR hosting account which will then allow YOU to add it to yours. I URGE YOU TO START THIS PROCESS AS SOON AS YOU CAN TO MINIMIZE DOWNTIME OF YOUR CLIENT'S WEBSITE.

The 72 hours has come and gone and because of a "backup in the processing queue" at GoDaddy, I still can't add my client's domain to my hosting account. From the time GoDaddy released the domain to me my client's site has resolved to the GoDaddy parked page. This is good in the sense that at least the former developer can't forward users to obscene content, but at the same time my client's site has been down for over 4 days.

This post serves as a warning to others that GoDaddy has a few kinks to work out in their hosting transfer policies. If you are researching information on what to expect in the process, be warned that the site you are transferring may experience down time while GoDaddy muscles control away from the previous owner. However, rest assured knowing that there is no interruption to email service, which to my client was the most important factor.

DSN-Less Database Connection to MySQL in Coldfusion

Have not tried this myself yet, but wanted to drop it here so we can play with it in the future.

A DSN-less connection is made completely through the code, without the need for configuring anything within the ColdFusion Administrator. All of the information for the connection is specified within the code. This includes the driver, servername, databasename, username and password.

To make a DSN-less connection to a MySQL database, the following code snippet can be used:

<cfscript>

classLoader = createObject("java", "java.lang.Class");
classLoader.forName("sun.jdbc.odbc.JdbcOdbcDriver");
dm = createObject("java","java.sql.DriverManager");

con = dm.getConnection("jdbc:odbc:DRIVER={MySQL ODBC 3.51 Driver}; SERVER=server; PORT=3306;
DATABASE=database; USER=username; PASSWORD=password;OPTION=3;");


st = con.createStatement();
rs = st.ExecuteQuery("Select * FROM table");
q = createObject("java", "coldfusion.sql.QueryTable").init(rs);

//the query is stored in the variable q

</cfscript>

Image Expired: Please Refresh The Page to View This Image

We've run into this problem before and so I've stolen the solution from the cfchart blogspot blog site:

Problem

The following message is shown instead of the graphs:
"Image Expired
Please refresh the page
To view the image"


Lot of people have faced this problem, the reason is the timeout in the caching engine of the Coldfusion keeps the charts for any request only for a default value of 5 seconds.
We missed providing an interface to change this value in the CF Admin, but you can still change this value by:

1. Stop the CF server.
2. Open <cf install path>\lib\webcharts3d.xml
3. You can increase the timeout for keeping the graphs in the cache by editing the minTimeout and maxTimeout attributes:

<?xml version="1.0" encoding="UTF-8"?>
<server image="PNG" cache="Memory" minTimeout="5000" maxTimeout="30000"....

change this to whatever values you want.(Values of minTimeout and maxTimeout are in milliseconds.)

The minTimeout and maxTimeout are per each request, i.e. the graphing cache will keep the graphs for each request for minTimeout amount of time. So if there are 4 graphs in one page then request for the page arrives at lets say 1'o clock and the min timeout is 5 secs, then each graph for the request will be kept only in cache for 1'o clock + time to generate graph + minTimeout. So a problem could be if the last graph takes lets say 10 secs to generate, then by the time it is ready all the previous graphs will timeout and will be removed from the cached.

This can create a problem when:

1. There are a large number of charts one page (> 200). In this case, some charts will be drawn but remaining charts will display the error message


2. There are only a few charts on a page but some charts take more than minTimeOut amount of time to generate in this case the remaining charts will not be generated and the error message will be thrown.

Start ESX or ESXi Guests at Boot

I've had to do this before and always forget, so here goes.

1. Launch the VIC
2. Click on the server icon (not the guest icon)
3. Click the "Configuration" tab
4. Click on Virtual Machine startup/shutdown
5. Click on "Properties"
6. Click on "allow virtual machines to start and stop with the system"
7. Click on the guest you want to start automatically and then click "move up" until it's in the 'Automatic Start Up' section
8. Rinse, repeat for any other guests OS's

The last few steps are not very intuitive, but you get the idea once you've done it a few times. Thanks to Merrick for reminding me which tab these settings were on. I had to do this a few months ago and had forgotten.