Reply
Newbie
Treo 700p (Sprint)
paideia
Posts: 2
Registered: 03-08-2007
0

airSAMStateMachine.c 3259 1510 error

I have an airSAM-error that I have not yet seen posted.

airSAMStateMachine.c 3259 1510

My Treo 700P no longer syncs unassisted. I'd greatly appreciate help/advice.

Thanks



Post relates to: Treo 700p (Sprint)

Newbie
Treo 650 (Sprint)
jahlewis
Posts: 1
Registered: 03-21-2007
0

Re: airSAMStateMachine.c 3259 1510 error

I'm getting the same errors on my 650
Newbie
Treo 700p (Verizon)
mikesharper
Posts: 1
Registered: 08-11-2005
0

Re: airSAMStateMachine.c 3259 1510 error

I am experiencing the same problem on my 700p and have reloaded versamail and ESA a couple times with no change. Have either of you been able to resolve the problem?
Newbie
Treo 700p (Sprint)
paideia
Posts: 2
Registered: 03-08-2007
0

Re: airSAMStateMachine.c 3259 1510 error

Frustrated with these error messages, I was playing with the various sync functions and I believe that hitting either "sync all" or "sync calendar" from the calendar cleared up the problem that caused the error message.  I'm sorry I can't be more specific - I wasn't tracking closely what I was doing at the time.
 
Best of luck
Newbie
Treo 650 (Verizon)
CassattIT
Posts: 1
Registered: 06-04-2007
0

Re: airSAMStateMachine.c 3259 1510 error

This error message nearly always happens with a corrupt offline calendar event.  The fix for this is:
 
  1. In Outlook, click on Calendar to view the calendar.
  2. Open the File menu.
  3. From File, select Folder, then Properties for "Calendar".
  4. Under the General tab, click the button for Clear Offline Folders.
  5. Your Calendar items may disappear. If this happens, you can restore them from the Exchange server later. For now, don't restore it.
  6. Perform a HotSync operation.
  7. Open the HotSync log and look for the OLERR message. If it's not there, you have resolved the issue.
  8. Whether or not OLERR returns, you can now restore your Calendar data from the Exchange server:
    1. In Outlook, open the Tools menu.
    2. From the Tools menu, select Send/Receive, then Send/Receive All.

Your Outlook client will contact the Exchange server and display your Calendar information from the server.

Newbie
Treo 700p (Sprint)
Razta
Posts: 1
Registered: 06-13-2007
0

Re: airSAMStateMachine.c 3259 1510 error

I just gave that a shot and it didn't work for me.  :smileysad:
Super Contributor
Treo 700w (Verizon)
Scifiaddict
Posts: 218
Registered: 12-22-2006
0

Re: airSAMStateMachine.c 3259 1510 error

Has the EAS account been checked on the server yet?
As per palm KB article 41831 the 1510 error implies  Sync interface: Account reset is required such as because it is not provisioned.
 
There may have been an update on the server everything ranging from a PW change to security patch being installed which may no longer allow the currently configured EAS user account of VM to sync.
Newbie
Treo 700p (Verizon)
rlotano
Posts: 1
Registered: 07-30-2007
0

Re: airSAMStateMachine.c 3259 1510 error

I'm getting the same error for the past week. Did anyone find a solution?
RL
Newbie
Treo 755p (Verizon)
Stanton
Posts: 1
Registered: 01-26-2008
0

Re: airSAMStateMachine.c 3259 1510 error

[ Edited ]
I have a 755p, Exchange (2003, I think) and Versa Mail keeps sending me the AirSam error message 1510. It works fine, but I just get the annoying message. "Outlook needs to reset your account."
 
Really frustrating.
 
This is my 3rd 755p in a month and I just can't seem to get a break. 


Message Edited by Stanton on 01-26-2008 07:18 AM
Regular Visitor
Treo 755p (Verizon)
grotte
Posts: 3
Registered: 03-06-2008
0

Re: airSAMStateMachine.c 3259 1510 error

My experience is that there is usually a calendar event that is causing the problem.

Steps I've used to fix this for myself.

1. In outlook, archive all calendar events older than ~2 weeks. Now see if the problem still exists. This doesn't effect repeating events that have an occurrence in the future.
2. Go to the calendar. Go to View->Arrange By->Current View->By Category. Look for calendar items with attachments. Delete them. See if the problem still exists. If not, you can try undeleting the events to see which one was the cause.