Friday, November 18, 2011

Windows Phone 7 Crashes while setting up Outlook Email to Exchange

The Background
I had dropped my phone one too many times and the front glass had cracked. The phone was still usable but I was tired of looking through cracks. It was also starting to act funny sometimes and not haha funny.
I had an an identical phone just sitting in a box and not being used I decided to finally move across to it. It was fairly painless. The only hitch I hit was while setting up my exchange email account on the phone.

The Problem
I clicked on the "Outlook" account and put in my email address and password. It then after a little while asked me for my username and domain name. This is most likely due to my username being a little different from my email address. I put it in and my domain name and clicked on. After a short period of time I got this message.
At the top it said "...and we've found them!" and then the error message "Oops! We're having a problem that we can't solve at the moment. Try again later."

This was confusing because I have 7 other phones just like this that are working just fine. Here were the differences that had happened between my previous phone and this phone.

  • All email with exchange had been setup pre-mango. Maybe something with Mango didn't jive with my exchange server. I doubt this one.
  • I had changed my username to where it no longer matched(don't think this is the issue)
  • Before we had a private cert and now we use a GoDaddy Cert.
  • I had also setup auto-discover settings to work
I feel this is something with our auto-discover settings(although outlook and other phone OSs don't have a problem with them outside of our network) since I had done this for other Phones to different exchange servers and not had a problem. I can't guarantee this which is why I put this post up.

The Solution
Windows Phone tries to ask for the least amount of email information when setting up an account. If it doesn't work it asks you for more information. Then if it doesn't work a second time it shows you advanced settings. Well I just fed it wrong information till it showed me advanced settings.

I then manually entered all the settings correctly. Since it doesn't need to auto-discover any settings than it instantly creates the email account and starts syncing. This allows you to bypass whatever is causing it to choke. After a short time it should then start pulling down your emails, tasks, contacts, and events.

I am now running it for a week on the new phone and enjoying it.

Tuesday, October 18, 2011

Essential Business Server Forefront Fails to Create Reports

The Problem
Error when trying to generate TMG Report
So as part of a need to start seeing who was sucking down my bandwidth than I decided I would take a look into the reporting that is included with Windows Essential Business Server 2008(EBS) on the Security Server which is Forefront Threat Management Gateway. I opened the Forefront TMG Console and after creating a report I then told it to "Generate and View Selected Report" This resulted in the error to the right popping up.

The report Web Usage could not be generated....

After trying various other variations of the report thinking that maybe there was some problematic data it was still giving me issues. At this point I decided to dig a little deeper into the error.

Error when browsing to site. (Click for Larger)
It was giving me a 500. That wasn't really specific so after some additional digging on the net for troubleshooting they recommended opening the URL in IE. and I should get the Report Server interface. Instead of that I got this screen. This was good because it told me it was a 500.0 error as well as gave me the following more info to use in my searching:

HTTP Error 500.0 - Internal Server Error
The page cannot be displayed because an internal server error has occurred.

Detailed Error Information
Module: IsapiModule
Notification: ExecuteRequestHandler
Handler:  AboMapperCustom-2299220
Error Code: 0x800700c1
Requested URL: http://127.0.0.1:9009/ReportServer$ISARS
Physical Path: C:\Program Files(X86)\Microsoft SQL Server\ MSSQL.3\Reporting Services\ReportServer
Logon Method: Neogitate
Logon User: (My Username)


I then started looking around this path and stumbled on a post about Coldfusion running on IIS7 and this error being created almost identically. The problem for that post was that Coldfusion was running as 32bit and IIS7 was 64bit. The Solution was to run a script that would enable 32bit web apps.

Well just glancing at the task manager I could see IIS was running 64bit and that the reporting server was running as 32bit. I also remembered that for the installation of an update that the EBS Blog had me enable and then disable this particular flag Enable32bitAppOnWin64. After hunting I found that entry http://blogs.technet.com/b/essentialbusinessserver/archive/2009/05/06/sql-2005-sp-3-kb-955706-fails-to-install-on-the-ebs-management-server.aspx

I decided to try this solution.

The Solution
Open an Command Prompt with elevated privledges on the security server and run the below script:
cscript %SystemDrive%\inetpub\AdminScripts\adsutil.vbs set w3svc/AppPools/Enable32bitAppOnWin64 1


After this I restarted the IIS Service. After this when I browsed to the web page it password prompted me. I knew that was a good sign. I then Jumped into the Forefront Report and pulled up my report. This time it worked without an error.

So my problem was either that that flag was set to disable since the beginning(never used the reporting server till now so not sure) or in following their blog entry to install the update for SQL Server it asks to set that flag to disable. They could have meant to just do that on the Management server but since their blog posts are a tad vague and the update was to apply to both so no was y of knowing if it was my goof or theirs.

Either way reporting is working now after hours of time on it. Now on to the next problem.

Friday, September 16, 2011

IE8 Error while installing. "Setup cannot continue because..."

The Problem
I was installing updates on a laptop running Vista x64. Mid install of updates it rebooted and then told me it was uninstalling some updates due to improper install of them. Which was fine. After the computer came back up I continued to install updates. Sadly I couldn't get Internet Explorer 8 to install due to it popping up the error "Setup cannot continue because a more recent version of Internet Explorer has been detected on this computer." I rebooted the computer and still had problems. I would usually ignore this but for other updates to show and progress I needed to get this to work.

I decided I would uninstall IE8 so it could re-install. After jumping into Programs and Features IE8 was no where to be found. So I then jumped online to see how to manually uninstall. Ran across a Microsoft Article showing the steps I had just checked earlier. No Go. They also showed a long command to run to get it to potentially uninstall the app. That didn't work either.

I then stumbled onto a forum post by "Chris Oliphant" on answers.microsoft.com. His post was my solution.

The Solution
I downloaded IE8 for my version of Windows. Make sure you have the right version x64 or 32bit. I ran it and got the same error. Leaving the box open I browsed to the Root of the drive. You should a folder there with a long numbers and letters name.

Open that folder and run IE8.msu.(You may need to copy the files elsewhere if you run into issues) It will not check to see if IE8 or 9 are installed and will just overwrite the install of IE8 that is on the computer.

After it is done installing reboot the computer. You can now delete that folder that is at the root of the drive. (Be careful don't delete something else and mess up your computer) Re-run Windows Update and it should then find the additional updates. You are then good to go.

Thursday, September 15, 2011

Avaya IP Office Paging Both Overhead & Phones Simultaneously - Updated

The Backstory
At some point in the past we moved to the Avaya IP Office platform for our VOIP system and I have been truly impressed with it. It really has not had any problems. Other than some FAX over IP issues it has been superb. The level of configuration has been great. We did run into another issue which I will mention below in the problem section.

We recently tied a remote location back to our main offices where we had our Avaya IP Office system. We also swapped out the old Avaya Partner system with 1608 and 1616 series phones. After this was done it was brought to my attention that they had an overhead paging system for a large shop and outside the building.

They needed to make this work. This was across a point-to-point T1. They also only wanted to page once and have it go over both systems simultaneuosly. I had already setup paging over the phones which covered the inside of the building.

The Problem
Now the problem was that even at another location where they had a bogen paging system, they had to page the phones and the overhead system seperately. This is because the partner we had worked with and avaya said it couldn't be done. Now if this is true, I don't know, but those I spoke to said that was the case. That was fine for the location where the avaya system was located nearby to do the page interface.

At the remote location their was no avaya system so even though the paging system existed at the remote location I didn't see an easy way to tie it into the Avaya Phone system. After working with a third party vendor they recommended. a MultiTech MVP130-FXS. We said it would tie in the paging system into the system so it acted just like a phone.

Well after much time and paying money for a Third Party IP Endpoint license. I found that it didn't work just like a phone. I also couldn't get it to interface with the Multitech without it issuing a dial tone. This was after some hours of just getting the unit setup. After speaking to Multitech it sounded like I was going to actually need two multitech devices. :(

At this point I was rather frustrated and knew the remote location was starting to get frustrated. I had now spent over $300 dollars and it looked like to get a partial solution(paging overhead and IP Phone seperately) I was going to have to spend more money and more time of which I had already used tons. So out of desperation came the following solution.

The Solution
Overhead Paging System Page In Port
So I had been plugging the analog port of the MVP130FXS into the Page In port of the overhead paging system. I could get ringing and a dial tone over the speakers but paging was a no go. I had a 1608 phone sitting next for me to test dialing the MVP130.

Out of frustration I realized that I could probably plug in anything that made noise into this guy. I took the cord out of the headset portion of the phone and plugged it into the overhead page in port not expecting much. After pulling the headset off the phone a dial tone came blaring out of the paging system speakers.

YAY, progress. So I called that extension and picked the headset off the unit to answer the call, it worked and I could hear my voice across the system now. I realized though that even if I setup the page button to just call this extension than I would still need something to lift the receiver or I would have the same issue as I had with the MVP130.

The paging to phones is sounded through the phones internal speaker. At this point I had my "aha" moment. I took apart the 1608 and found the speaker. It had 2 wires running to it. I took the previously Paging cord which had a RJ11 on one side and the two middle wires stripped on the other side. I then plugged the RJ11 side into the page in port of the overhead, and rapped the two wires around the two connectors of the phone. Giving me what you see below.

The Phone had already been a part of the page group so I had them do a demo test and it worked perfectly. So the end solution is to take a 2-wire from the speaker of the Avaya IP Phone to the page in on your system. This also allows the overhead and phones to page at the same time. This is said not to be possible with the Avaya IP office system.

I actually had to return this phone back to another location and brought a spare 5621 to use in it's place and it worked great. So I believe any phone that worked with the Paging system of the Avaya IP Office would work, but test. What I plan on doing though for long term use will be to purchase a 1603-I from Dell running at $100 with a Power adapter for $8. I will then open the unit up and solder a 2 wire two the speaker connectors and cut out a small hole at the bottom so I can seal the unit back together. I would then attach run that wire directly to the paging interface as needed.

NOTE If this phone is part of a Hunt Group than make sure you turn the ringer volume all the way down so your staff doesn't go crazy hearing the ringing going over the overhead. Also I had a sticky note keeping the receiver trigger from noticing the headset was off the hook.

NOTE 2 The Phone volume can be turned up and down if it is either too loud or quiet across your paging system or adjust it on the system if you can.

The Wrap Up
So instead of spending upwards of $500 to get the equipment and licensing to make a half-working solution I can spend about $120 and have a fully working solution that is quite powerful. You can even setup another paging short code if you want to just page one or the other instead of both at the same time.

Now this is not blessed by Avaya and as typical I am including a warning that this could damage your paging system and you are performing this hack at your own risk. Obviously the phone you are operating on you won't be able to use for a phone but it is way cheaper than the alternative and a great solution for bringing paging to a remote location.

I have not tested this with a Bogen but have another location that I will be testing this on in the next week to see if the Bogen amp will be hospitable to this "Hack."

Update 9/26/2011
I tested another location with Avaya branded paging module tied to a 5621 phone. Worked fine. To the right is an attached picture. I just tied the two lines from the speaker on the phone to the phone system pins on the Paging Module. You may have to adjust the volume on the phone.
Updated 10/18/2011
I ordered a 1603-I with a power adapter. I took it apart and soldered my two wires from a Cat 5e cable two the speaker leads. I then drilled a hole in the back of the case just the size of the cable and routed it out the back and over the the paging interface crimping down the two wires to it. Also mounted the phone to the wall. Sadly the picture freaked out so you can't see the cables running across. As you can see to the right though it looks alot nicer and the phone is actually functional if they need it in there, just don't use the speakerphone.

Fixing HL2070N Toner Life End Error

The Problem
The error on the web interface of printer
We had someone who was having a problem with a printer. It refused to print. I was called in and upon looking at the printer on the computer it showed it was initializing. I tried a test print and nothing happened.

Upon viewing the web interface for the printer interface I noticed that the toner light I saw let wasn't was because it was low on toner but because the device thought it was done or out.

At this point I asked the person about the toner and they said that they had recently replaced it. OK well that wasn't the solution. I jumped online and across a couple of forms I found my solution.

The Solution
The printer uses a digital Eye to see the level ov toner in the device. If you pull out the toner than on either side where the grey(on mine) is  a circle that associates with a window through which the printer can see.

Either due to this one cartridge being faulty or myabe the printer, the printer didn't like what it was seeing or maybe could see through which would indicate no toner. No toner wsn't the case due to great print jobs, new cartridge, and gentle rocking to ensure proper toner distribution . I guess we'll see with new cartridges in the future.

Sticky note blocking toner window 
To overcome this I took one of those small 1"x2" sticky notes and tore out a section and dropped it in front of the clear window on the right side(As shown in the picture to the left).

Putting the cartrdige back in the web interface no longer displayed such an error. I was also then to continue printing. This error has not returned either after a short period.

The hope is that this was just one cartrdige causing the problem but it could mean something failing with that digital eye system. Hope this saves others of you out there money not needed to replace a cartridge or printer.