Month: May 2009

Hospital tech.

Kristen woke up in the middle of the night with chronic stomach pains and so at 5am I was searching through the United Health Website trying to find the nearest Hospital/ER to where we are staying. The strange thing is that the hospital 11 miles away was not listed. However this doesn’t seem to mean it is not “in-network” as other hospitals were listed ok. Their 24hr careline is only open from 8am to 8pm which is not much use when trying to find out whether your hospital costs are going to be less than $3600 or up to $10,000
So, we ended up going to the hospital anyway as by that point Kristen was in too much pain. The hospital was pretty good with not a lot of waiting to see someone – thankfully Kristen has been ill early in the morning both times we’ve had to go to ER so we’ve not had to wait for too long. Whilst Kristen was being looked at I was reading my book (when the needles came out) and looking at the technology during other waiting periods.
The triage area was computer driven using citrix to connect to their health system. This seemed to be a little slow, but still faster than the triage nurse could type. Extensive use of lookups ensured that data was entered correctly into the database, but meant that “daily” was not recognised and therefore a lookup was provided with options such as WEEKLY or DAILY. You’d have thought that the nurses would have realised to push the caps lock button OR a UCASE function made to ensure that the text typed in was correctly matched. I must admit I was impressed at the medicine lookup – it must be pretty tough keeping all the medicines in the db up to date.
GoogleShirtWhen we were moved into the ER Room itself, I was suprised to see a computer mounted high up on the wall with a flat screen monitor on a swing out arm. I was also surprised to see that they were running Novell for their network (and Mcafee antivirus). I wasn’t sure why the people would need icon’s on the desktop for “my computer” and network neighbourhood – with a locked down desktop I would have thought that the programs needed would already be on the start menu or the desktop.
One of the amusing conversations occurred when one of the nurses took a double take at the t-shirt I was wearing (shown in the picture) and then said that my t-shirt looked familiar. I really would hope that the Google logo is now familiar to most people!

The final analysis is that Kristen likely has a kidney stone on it’s way out, but as the CAT scan equipment is broken we won’t really know for sure (although all the signs are there that this is the case). For an amusing (PG rated) description of Kidney Stones, read this Blogography Kidney Stone metaphor posting.

Dynamics SL crashing on startup after installation of .net patches.

Overnight several of the .net patches were pushed out to workstations and now when Dynamics SL  is run I get the following error. “Microsoft Dynamics SL has encountered a problem and needs to close. We are sorry for the inconvenience”

Looking in the event log or the details  I see a .net Runtime 2.0 error, Event 5000. Description EventType clr20r3, P1 msdynamicssl.exe, P2, P3 4889f859, P4 solomon.kernel, P5, P6 4649b3d9,P7 1b4, P8 0, P9 system.accessviolationexception, P10 NIL

This is then followed by id 5001, Description “Bucket 300554837, bucket table 5, EventType clr20r3, P1 msdynamicssl.exe, P2, P3 4889f859, P4 solomon.kernel, P5, P6 4649b3d9,P7 1b4, P8 0, P9 system.accessviolationexception, P10 NIL

The cause of this was actually the installation of a .NET Framework 3 patch.

The sorry saga of trying to fix this solution is documented at the dynamics forum but this is a known issue and the patch is available through Customersource or PartnerSource if you have access to this. Alternatively call Microsoft hotfix line on 1 888 456 5570 and request the Dynamics SL hotfix 961802. There is no charge for this hotfix.  Install on your workstation and you should be good to go.

However if you have tried to fix this issue by editing your .NET framework settings then I recommend totally removing .net from the computer, reinstalling v2 and the service pack.  There is a really good tool for removing .NET framework from Aaron Stebner which works a treat.

Windows 7 Upgrade advisor ran into a problem

I downloaded the Windows 7 upgrade advisor from Microsoft, that is currently in beta on both my work and my home pc to see what the differences were. The work laptop had some warnings but the software fails on the home pc. I get a very unhelpful message of “Windows 7 Upgrade advisor ran into a problem scanning your devices. Upgrade advisor needs to be able to scan your devices to determine if your computer is capable of running Windows 7. Please let us know about this problem.”

Unfortunately there is no UI to send the feedback to Microsoft and there is nothing on the download page either.

Symantec Enterprise Protection (SEP) firewall requirements for client checkin.

So I’ve spent ages troubleshooting and debugging Symantec’s Endpoint Protection (SEP) version 11, MR4 – the first version that actually has a hope of working  on a 64bit platform.  After spending far too long configuring the various policies and tweaking various settings I was finally able to get the software installed via group policy on a testlab machine but the client would not checkin with the management server. The virus definitions were 4 months old BUT the client console was saying everything was ok. Lots of troubleshooting later and I stumbled across the definitions for the Management server – a setting that I had originally wanted to change anyway.  In there I saw that the management server was listening on port 8014 and a quick telnet check from the client showed I was unable to connect.  Disabling windows firewall (temporarily – this is on a testlab so the infection risk is minimal) allowed the client to check in with the server, change some settings in the console and update the virus definition dates. Finally I re-enabled the firewall, added an exception for TCP port 8014 and it all looks good, but I’ll wait to see what happens overnight for definition updates on the client.  For future reference the list of communications ports for version 11 can be found at Symantecs website here or posted below in the extended entry.

Installing 32 bit printer driver on Windows200864 server

Tried to install a 32 bit driver for the Dell 2330dn printer but the software kept asking me “please provide path to windows media (x86 processor)’”. Pointing the dialog box to the x86 directory or the i386 directory that came with the print driver didn’t help. Neither did pointing the dialog to a copy of the i386 directory from an xp cd. A reply posting on Microsoft’s technet site gave me a hint to get this working. By first installing and sharing the 64bit driver, it is then possible to install the printer by using the following steps.
On a 32 bit (in my case XP) workstation, navigate to \\servername and then double click on the printer that was previously shared.
When it asks for the driver location provide the location to the i386 directory of the extracted driver.
Verify once installed that the driver is now successfully listed as an option on the printer by clicking on the sharing tab and then the additional drivers button.

Backup Exec “low disk space” warning.

I had an annoying case this morning where Backup Exec was refusing to write to a removable hard drive after it had got to the point where the disk was full. Even deleting old data on the drive, restarting services would not get the software to continue writing to the drive which now had 250gb of empty space.

In the end, right clicking on the device and selecting pause, then right clicking and unpausing the device fixed the problem. Simple when you know how but frustrating when nothing else seemed to work!