Viper Key FOB replacement Pairing\Programming

So I recently went through the fun of programming a new 7251V Viper 2-Way LE Responder
Remote Replacement for my Prius. I figured I would save anyone else out there the trouble that I had with the programming. I noticed all of the information on the internet was not enough to actually get it working on a Prius. So here is how I got it working on my 2009 Toyota Prius.

1st you need to enter the remote into progamming Hold the Function button until the remote gives a long beep and LED light comes on the remote a (it takes about 8 sec.) Then press and hold the remote start buttom until the remote beeps 3 times and LED lights up. Now your ready to program the remote, you have 60 seconds to do the steps in the next 2 paragraphs.

One of the door has to be open . Turn on Prius so it says "Ready" and the ignition is fully on (this is the important part that none of the other forums talks about, the car must be running). As soon as you turn the car on you have 5 seconds to do the next step which is to press and release the control center button (Control center is just the antenna that is mounted on you windshield, it should have a blue light and a button that you can press). After you have done that you have another 5 seconds to press and hold the button after roughly 5 seconds of holding the button down the blue light will start blinking and if you have the system hooked up to more than just remote start and doors you may hear a chirp or horn honk, but in my case neither apply so I had to watch for the blinking light because that was my only indication.

Then you need to press the lock button on the remote and you will hear a success tone from the remote and maybe a chirp from the Viper system. After you are done with that you can turn the car off and hit the function button twice to exit and save the programming\paring information.

Does that help? I know this info would have helped me big time when I was going through it so I hope I can help others.

Thanks,
-Spader

How to disable Sirius XM Timeout

If you're like me and listen to the Sirius XM online radio 24/7, then the 90 minute streaming timeout really gets annoying.  We'll I've got the solution for you.  I have done this in Chrome and Firefox and it works great.

In summary to disable the streaming timeout you need to disable the JavaScript (JS) on the page after you have started the streaming session.  It won't work if you disable JS before logging in because it requires JS to log in.

I recommend using Chrome because the Extension from this location does a great job of disabling the java only on the Sirius XM tab and other tabs can continue to use JS.

The other option if you don't like Chrome is to use the QuickJava add-on in Firefox.  Some downfalls I have seen with this is that it diables JavaScript in all tabs, and it goes on to disable JS in your other Firefox installations if you have the QuickJava Add-On installed there and enable Sync in your Firefox browser.  To use this plugin you have to make sure you go to View --> Toolbars --> Add-on Bar then you can click on the JS at the bottom of the Firefox page.

SBS 2003 OWA failures

So I was starting to have issues with a SBS 2003 server that I manage.  For some reason the OWA service would stop working for exactly an hour, and sometimes more, then all of the sudden it would come back online.  Because I knew the time it went down and came back on within a minute I thought I would see logs during that time but that was not the case.

Well I  have finally found what was causing the issue.  It is ISA server that is blocking the connection because of a timeout issue.  I didn't make any changes but this just started happening out of no where.

Here is the error log that I was receiving in the ISA Monitoring logs:

Failed Connection Attempt	SERVER 10/24/2011 8:16:40 AM
Log type: Web Proxy (Reverse)
Status: 10060 A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
Rule: SBS Web Publishing Rule
Source: External ( 64.141.100.136:0)
Destination: ( 65.41.114.173:443)
Request: GET https://mail.server.com:443/Remote/logon.aspx?ReturnUrl=%2fremote%2fDefault.aspx
Filter information: Req ID: 16e41712
Protocol: https
User: anonymous

I have fixed this issue by modifying this time out in the firewall policy under the SBS Web Publishing Rule, In the advance setting under the SBS Web Listener Properties, I change the Connection Timeout from 120 to 620:


Let me know if you have any questions,
-Spader

Exchange 2003 Errors SBS 2003

I found a warning message in the Application logs on my Exchange 2003 server and here is what I did to get rid of the error within the logs.

*****************************************************************************

Event Type: Warning
Event Source: MSExchangeMU
Event Category: General
Event ID: 1040
Date: 10/19/2011
Time: 4:24:51 PM
User: N/A
Computer: SERVER2011
Description:
Metabase Update failed replication 5 times with error 80070003 (The system cannot find the path specified.). Please change the diagnostic logging level of MSExchangeMU to 'minimum' or greater to find the source of the problem.

For more information, click http://www.microsoft.com/contentredirect.asp.

*****************************************************************************

So I found some steps on the web which directed me us the MetaEdit tool to delete a key.  I ended up only deleting the DS2MB key and not touching the SMTPSVC/1/domain key.  This completely eliminated all of the warnings related to the issue and now OWA is working like a champ.

Download the tool here:
http://support.microsoft.com/kb/301386

Follow these steps:
1) Backup the IIS metabase
2) Stop the Ms exchange System Attendant service
3) Using Meta Edit delete/rename the DS2MB key (Metaedit is a free tool)

4) Using Meta Edit delete/rename the key SMTPSVC/1/domain
5) Restart the Ms Exchange System Attendant service
6) The above keys will be recreated


Below shows the errors and how they stopped at 4:39pm when I executed the steps above:

Hope this helps others!
-Spader

BeyondPod Feed Update Disabled

I believe I have finally figured out why my Beyond Pod scheduled feed update keeps getting disabled.  I was thinking that it was Advanced Task Killer that was killing BeyondPod but that was not the case.  I already put BeyondPod on the ignore list so it wouldn't automatically kill that program.

I figured out that it was my Titanium Backup program that was doing a force kill on the program so it could back it up.  So if you have the same issue with BeyondPod feed update getting disabled all of the time, just go into your titanium backup program and either create a filter so it doesn't backup BeyondPod, or change the settings on Titanium Backup so it does not force kill applications.  I would suggest creating a filter because if Titainium Backup doesn't force kill the application it won't be able to back up many programs properly.

Later,

-Spader

Dyndns Standard SMTP Service not working

All,
I experienced an issue this morning with my dyndns service.  I use them to send all of my email from my exchange server to external recipients.  It appears they forgot to renew their certificate on the their receivers.  These are the errors that I'm receiving on both exchange servers that I manage.

451 4.4.0 Primary target IP address responded with: "454 4.7.5 Certificate validation failure."

I also so in my logs event 11005 that stated this: Unable to validate the TLS certificate of the smart host for the connector MailHop Outbound. The certificate validation error for the certificate is CertificateExpired. If the problem persists, contact the administrator of the smart host to resolve the problem.

So I came to the conclusion that DynDNS forgot to renew their cert. Oops!

I notified them and they stated this:
I have received and acknowledged your concern regarding messages not being able to be sent through our outbound.mailhop.org server or generating a certificate-related error message.
At this time, Dyn is aware of a couple of our servers experiencing issues with their certificates and we are working towards a resolution of this issue.

To temporarily alleviate the issue, we kindly ask that you retry sending your messages with TLS turned off in your mail client. We will post an update to our status.dyn-inc.com site as soon as the issue has been resolved.

That said, if you are managing SBS 2008 or Exchange 2007 here is how to disable TLS quickly:

Just uncheck the "Basic Authentication over TLS" and viola!

Let me know if  you  have any issues with this.

-Spader

UPDATE 10-07-11: I am still having issues with my Exchange 2007 server, but the other server that I support which is exchange 2003 started working at 8:46am on the same day that the issues started 10-3-11.

I definitely which they would figure out how to be compatiable with exchange 2007, I'm sure many people are running this and having issues.  Here is the error message that I'm receiving on my exchange 2007 server (SBS 2008):

Log Name:      Application
Source:        MSExchangeTransport
Date:          10/7/2011 7:47:58 AM
Event ID:      11005
Task Category: MessageSecurity
Level:         Error
Description:
Unable to validate the TLS certificate of the smart host for the connector MailHop Outbound. The certificate validation error for the certificate is UntrustedRoot. If the problem persists, contact the administrator of the smart host to resolve the problem.

It looks like they are either using a self signed certificate or used a certificate authority that is not in the SBS 2008 trusted root CA list.

PLEASE fix DynDNS, I would like to enable my encryption!
-Spader

UPDATE 10-19-11: I randomly checked to see if DynDNS has fix their issue today and finally was able to send messages using encryption.  Thank you for finally fixing your issue DynDNS.  We are finally back to normal!
-Spader

Acer Iconia A500 GPS issue

Is anyone else having issues with the Acer Iconia GPS?  I can't get it to get a GPS fix, and if it does it will take at least 2-10 minutes to get the fix then it doesn't keep the fix.  I think something is seriously wrong with their GPS in this tablet.

I also tried using GPS Status app to try to fix it because that works on my HTC EVO but I didn't have any luck.

Did anyone find a way to fix this?  Do I just call Acer support and try to get new hardware or a software patch?

Thanks!
-Spader