Several 9to5Mac readers noticed a rather peculiar phenomenon this last week — their freshly-ordered Verizon iPad 2 units shipped all the way from China just fine, only to boomerang back to sender right before delivery time. Now, Reuters has the official word: Apple’s recalling an “extremely small number” of Verizon iPad 2s which were flashed with a duplicate MEID code. Should they have been delivered, users would probably have found themselves unable to connect to 3G, or booted off before long, as Verizon reportedly can only have one device with that unique identifier on the network at once. We’re not sure whether to applaud, but it’s good to see manufacturers taking responsibility for their hardware before it hits shelves.

Update: We spoke with Apple about this, who wouldn’t give us much beyond the official quote — which is, for the record: “Duplicate MEID codes were flashed onto an extremely small number of iPad units for the Verizon 3G network.” That said, we were able to confirm that a few of these 3G iPad 2s sneaked through and got into the hands of customers. Apple is, of course, replacing those free of charge, so if you’re in possession of a brand new iPad that was never able to get on 3G… you know who to call.

[Thanks to everyone who sent this in]

Apple returns a few Verizon iPad 2s to sender (updated: some got through) originally appeared on Engadget on Sat, 11 Jun 2011 18:11:00 EDT. Please see our terms for use of feeds.

Permalink   |  9to5 Mac, Reuters  | Email this | Comments

Another issue appears to be plaguing those who’ve upgraded to iOS 4.3, though thankfully this one won’t make them late for work. We’re seeing dozens of reports online of iPod touch users, particularly those with fourth generation models, who are seeing odd graphical glitches since updating to 4.3. These are most noticeable on the lock screen, as you can see above and in the focus-challenged video below, but people are reporting other issues as well, like overlapping icons and other pixel oddities. If you’re seeing similar weirdness make sure you chime in down at the support forums linked below — oh, and feel free to click in the poll as well.

View Poll

[Thanks, Jesse]

Continue reading iPod touch showing freaky graphical glitches after iOS 4.3 update? (video)

iPod touch showing freaky graphical glitches after iOS 4.3 update? (video) originally appeared on Engadget on Tue, 15 Mar 2011 10:18:00 EDT. Please see our terms for use of feeds.

Permalink   |  Apple Discussions (1), (2)  | Email this | Comments

It hasn’t gotten quite the attention of the iPhone 4′s antenna problems or its proximity sensor troubles, but iOS 4 has caused some heartbreak for corporate users who connect to Exchange servers — checking mail or syncing contact and calendars can stall out interminably, with no option but to restart and try again. We’ve definitely had this problem ourselves, but happily Apple’s right on the case with this one — iOS 4 users who need to get their Exchange on can download an updated configuration file that seems to make things better. The new settings don’t seem to do much other than increase iOS 4′s idle timeout, but if it works, it works — and in our limited testing things appear to be going swimmingly. Okay, that’s one — now let’s polish up the rest, shall we?

[Thanks, Paul]

Apple patches iOS 4 Exchange issue originally appeared on Engadget on Wed, 30 Jun 2010 20:43:00 EDT. Please see our terms for use of feeds.

Permalink   |  Apple  | Email this | Comments

Comments I found when searching on the net for reasons.

Comments Massimo Luinetti (Last update 5/12/2007):
If you have performed an upgrade from version 2003 to version 2007 and you have only one configuration database, you will probably have to disable the old “SharePoint Portal Administration Service” (version 2003). That was the solution in my case.

Michel Dawidowicz (Last update 1/28/2005):
In my case, this symptom started to appear when the database backend was down for a short period. The event is logged twice per minute in the log. To resolve this restart the “Sharepoint Portal Administration” service on each affected server of the farm.

Ionut Marin (Last update 11/3/2004):
From a newsgroup post: “Go to IIS manager, open each site, and go to the home directory tab. Then, there is a section at the bottom called Application pools. Edit each and set the account to someone who has logon as a service right to the local server”.

The website troubleshooting tips wern’t all valid expect for this paragraph and changing “Services” logon information manually:

Use one of the following methods as appropriate to your situation:

a. If Windows SharePoint Services 2.0 is installed on a member server:
1. Click Start, point to Administrative Tools, and then click Computer Management.
2. Expand Local Users and Groups, and then expand Users.
3. Right-click the account that is used by the application pool for the virtual server, and then click Properties.
4. Click the Member of tab.

Restart IIS after these steps and check site in your browser.

http://support.microsoft.com/kb/823552