Fire and Brimstone

Just after I got the Brabus I managed to hit a *large* pothole on a country road. No, I didn't see it coming - it was dark... The tyre went flat and I took it to my local tyre place. "'Ere, did you know there's a dent in the rim?". Surely not(!). "If it goes down again, then it need fixing". It never went down again. It went through two Merc services. "Did Sir know there's a dent in the rim? If the tyre goes down, it needs fixing." It still hasn't gone down after 11 months.

Now, a few days ago I tried to tax the smart online. 'No MOT found.' I think I can say for certain that ANPR Cameras don't flag "no MOT's" on the grounds that mine ran out last October.

The MOT man gave me a severe talking to. "This could have exploded, killed someone, caused The World To End" etc etc. It still hasn't gone flat. However, a red ticket is still a red ticket.

I rang Lepsons. They had a week's waiting list. A quick trip through Yellow Pages found a place in Meopham call RimTec (or possibly Rim Tec).

"Ok, £20 per dent and I can do it tomorrow, by the way did you know you have six dents in the rim?"

Well, that's the brimstone bit, the fire is in, fitted and works great, only the decorating to do now...

Comments

Post a Comment

Popular posts from this blog

"The delivery extension for this subscription could not be loaded" when using SSRS

Image
OK, so we upgraded our server farm and put on the latest "stuff" (SSRS, SQL Server etc.) and the engineers gave me two servers to play with - SQL01 & SQL02. The idea being that we used high availability to help keep the factory running. We employed a contractor to load up and configure everything. At this point I wasn't involved. My involvement was to move all the reports and subscriptions from the old servers to the new ones once the servers had been configured. All went swimmingly, until I actually started to fire off the subscriptions to test them. Randomly (like 5 out of 10) I got the error in the title. I would edit the failing subscription and/or change the schedule time and it would work. I finally got around to moving 81 subscriptions for the same report (all slightly different parameters going to about 6 different engineers). I press the "go" button and every single one failed. Let's cut out the long story about how I went through about
Read more

Oooh, look, an Eagle...

Image
The Scottish Holiday . After the trauma of the Astra-breakdown episode and the gutless hirecar, we'd recovered sufficiently to begin to enjoy the rest of our holiday with our friends at the Castle... Chapter Seven: One of the things my wife really wanted to see was a seal, or seals if she was really lucky. So we decided to take a day out and around the Mull Of Kintyre. We stopped at "St Columba's Footprints" and carefully studied the jumbled collection of rocks and seaweed. "No seals there dear, let's carry on" "Oh, alright then, never mind. But that's where we were told they are most likely to be." We drove on and took a gated road signposted " To The Lighthouse ". This took us right up into the hills. As we were driving slowly along admiring the view, my wife whispered quietly... " Ooh, look an Eagle! " "Stop that, that's not funny." "No, really. Stop the car."
Read more

SQL Server 2008 / Reporting Services

Image
Since this has taken me four days to solve this one and, with almost no help from Google, I thought I'd log it here in case anyone else has this most bizarre problem. Scenario: You retrospectively install Reporting Services to an existing installation of SQL Server 2008. You try to configure it using "Reporting Services Configuration Manager" and as soon as you click "Find" you get "Invalid Class" 1 and no other information. These two links gave me the clue, they're essentially both the same. What they say is to run WBEMTEST 3 and connect to the Reporting Services WMI thingy. Then run the query, " SELECT * FROM __NAMESPACE ". When I did this I got: Note: TWO entries. The second one was a test database I had installed months ago and had removed at some point when I worked out that using the default instance of MSSQLSERVER was more convenient - but the registry(?) entries were still hanging around. I selected it by clicking o
Read more