Jump to content
demonfox13x

Lion GM Facetime error

84 posts in this topic

Recommended Posts

"The server encountered an error processing registration. Please try again later."

 

No matter which account i use i get this error when trying to log in. Accounts work fine in snow leopard. New facetime is version 1.1. I cannot roll back to 1.0.2 on Lion. While searching on google it appears to be a certificate problem but there is no matching certificate. Console logs look like:

 

imagent: [Warning]    Failed response from cert init: -44006, deleting context
imagent: [Warning]    Cleaning up validation info

 

Anyone having the same problem with lion GM or any DP version?

Share this post


Link to post
Share on other sites
Advertisement
"The server encountered an error processing registration. Please try again later."

 

No matter which account i use i get this error when trying to log in. Accounts work fine in snow leopard. New facetime is version 1.1. I cannot roll back to 1.0.2 on Lion. While searching on google it appears to be a certificate problem but there is no matching certificate. Console logs look like:

 

imagent: [Warning]    Failed response from cert init: -44006, deleting context
imagent: [Warning]    Cleaning up validation info

 

Anyone having the same problem with lion GM or any DP version?

 

This is due to the Certification error.

 

1. In Spotlight type in "Keychain Access"

2. There will be a certificate issued by Apple iPhone Device CA - This certificate was signed by an unknown authority. Delete this certificate (or move it to the desktop, out of the keychain access store)

3. Launch Facetime and login - this time there will be no error.

 

That helped a lot of users in the beta stage. If this solution didn't know then there maybe a new certification ready from Apple and need to be updated.

Share this post


Link to post
Share on other sites

Thanks for the reply but theres no such certificate that exists in keychain access. Ive searched google extensively and haven't found a solution yet. A reinstall of Lion did not work either.

Share this post


Link to post
Share on other sites

I have the exact same problem (only in the hack, the macbook works perfectly). Tried several options like removing or modifying certificates, deleting facetime preferences, etc. but no way.

Share this post


Link to post
Share on other sites

Maybe this will fix the problem.

 

Certs usually reside Keychain Access (KA) > login > My Certificates [under category]

 

Go to the above navigation and look for the certs listed and select one by one and you will see the details above like this.

 

"Issued by: Apple iPhone Device CA"... Do a backup and delete.

 

Quit KA and then launch FT. If the problem still exist. Go to KA again and import the cert back to the My Certificates and follow these steps.

 

1. Right click the cert and Get Info...

2. Expand Trust and then select "Always Trust". usually "Use System Default" is selected by default. Change to Always Trust and close that window and enter the system admin password.

3. Right click the imported certificate and select "New Identities Preference"

4. In the Location or Email Address: box paste this URL "https://registration.ess.apple.com/WebObjects/VCRegistrationService.woa/wa/register" and click Add.

5. Quit KA and restart the system and launch FT again.

 

Most likely this should fix the problem. If still throws error then Apple should reissue a newer certificate which will update this issue.

 

Cross your fingers :thumbsup_anim:

Share this post


Link to post
Share on other sites

The whole problem is i don't have ANY certs at all lol. THis is a fresh install of Lion GM and i don't have any certs in keychain

Share this post


Link to post
Share on other sites

I only have a few certs and none are signed by iPhone Device CA. When we navigate to that URL in safari it asks me to choose which certificate to use in a drop down menu but i have none.

 

Could this have anything to do with our ethernet controllers? I recall people having trouble signing in to the App Store where it said something about a GUID error. The "EthernetBuiltIn=yes" flag in boot plist fixed that problem. Ive got a Yukon 88E8056 and RTL8110SC, neither of them work with FaceTime.

Share this post


Link to post
Share on other sites

Has anyone tried this on Lion GM running on a real mac? I bet the actual issue is that Apple's servers aren't updated with the Lion GM certs.

Share this post


Link to post
Share on other sites
I have the exact same problem (only in the hack, the macbook works perfectly). Tried several options like removing or modifying certificates, deleting facetime preferences, etc. but no way.

 

This guy has it working on the macbook and their aren't widespread reports of it not working on Lion in the Apple support forums, so i doubt thats the issue.

Share this post


Link to post
Share on other sites
This guy has it working on the macbook and their aren't widespread reports of it not working on Lion in the Apple support forums, so i doubt thats the issue.

 

 

Doesn't work with my macbook pro so i don't think it's a hackintosh issue.

Share this post


Link to post
Share on other sites
Doesn't work with my macbook pro so i don't think it's a hackintosh issue.

 

As expected. Use your brains, people. The only things that don't work on hackintosh at this point are things that rely on EFI being there (FileVault 2: full disk encryption) or the bootrom (Boot Camp)

 

You didn't modify the installation image to remove some certificates to get it to boot/install, so why would you be missing certs? Think, people.

Share this post


Link to post
Share on other sites

no need to be cheeky, everyone here is here to learn. if you dont have the patience to explain without being condescending you shouldn't bother replying.

Share this post


Link to post
Share on other sites
That's where you are wrong. There is a great lack of intelligence in this community. You guys should worship what (intelligence) is given to you, regardless of the attitude I give it with.

 

I agree with the above poster...MYWomg...if you don't have anything positive to say done post. Thats the problem with people in these types of Forums...they think because they got it to work everyone else should not have problems. I have mine working, however, I don't mind helping people that need help. Thats what this forum is all about....

Share this post


Link to post
Share on other sites
I agree with the above poster...MYWomg...if you don't have anything positive to say done post. Thats the problem with people in these types of Forums...they think because they got it to work everyone else should not have problems. I have mine working, however, I don't mind helping people that need help. Thats what this forum is all about....

 

 

Could you export your certs so we could import it in ours ?

Share this post


Link to post
Share on other sites

Well I exported the cert from my Macbook to the HackPro and it does not work at all. Also the cert seems to be the same, no any noticeable difference between files.

Share this post


Link to post
Share on other sites

Guys... Export or somebody sharing their certs is not going to help in any kind.

 

Coz when Apple signs their certs, they usually encrypt some data with your mac address or your serial number.

 

But there are other chances too. On first install, they may just capture some data and encrypt with your cert and then store it into the Keychain Access.

 

I am a Mac user and not using HCKINTOSH ;) Maybe Apple will release a cert with and transfer it over when the official LION is out in the market.

 

But I do suspect there is something more than the cert. All these cert usual during beta stage throws an error when you read the console. Maybe you guys should see what kinda error FT throws when trying to sign in.

 

Maybe that will help us here to figure it out.

 

Cheers

Share this post


Link to post
Share on other sites

OK this is the console output when FaceTime is opened:

 

07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: CMIOGraph 0x7f7fcb49bd80:
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime:   Membe
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: r Nodes:
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	node  1 [ 1][ 0]: desc tinp dal  appl, instance 0x7f7fcb4a0cd0 O  
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	node  2 [ 3][ 0]: desc tdmx mstr appl
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: , instance 0x7f7fcb49f170 O  
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	node  3 [34][ 0]: desc tufc vtdc app
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: l, instance 0x7f7fcb49f280 O  
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	node  4 [25][ 0]: desc tefc vsyn appl, instance 0x7f7fcb4a1c70 O  
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	node  6 [
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 35][ 0]: desc tufc vtcm appl, instance 0x7f7fcb4aacf0 O  
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	node 12 [16][ 0]: 
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: desc tout 2prc appl, instance 0x7f7fcb4af1c
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 0 O  
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime:   Connections:
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	node  1 bus  0 => node  2 bus  0
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	node  2 bus  1 => node  4 bus  0
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	nod
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: e  4 bus  0 => node  3 bus  0
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	node  3 bus  0 => node  6 
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: bus  0
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime: 	node  6 bus  0 => node 12 bus  0
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime:   Events to be updated:
07/07/11 17:30:09,323 [0x0-0x3e03e].com.apple.FaceTime:   CurrentSta
07/07/11 17:30:09,324 [0x0-0x3e03e].com.apple.FaceTime: te:
07/07/11 17:30:09,324 [0x0-0x3e03e].com.apple.FaceTime: 	mLastUpdateError=0, eventsToProcess=F, isRunning=F

 

And this is the output after trying signing in:

 

07/07/11 17:31:51,381 imagent: [Warning]   Cleaning up validation info

Share this post


Link to post
Share on other sites

Seems there is no connection error.

 

Usually it should throw invalidation error if it is not signing in properly.

 

Surprised it just cleans up validation info without any error.

Share this post


Link to post
Share on other sites

I m having this issue as well but with the actual release of lion likely in the next few days I m not gonna worry bout it too much

Share this post


Link to post
Share on other sites
I m having this issue as well but with the actual release of lion likely in the next few days I m not gonna worry bout it too much

 

So you think with the official version of Lion we wont have this problem? I was trying to get my app store and face tie to connect in cause I needed to file this same solution for the official version. I hope it all works...

 

Is thursday the release day of Lion?

Share this post


Link to post
Share on other sites

Not entirely sure but i dont see the point of fixing it now only to have to fix it again once i install my retail version of lion

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

×