Ax2012 - Error Importing a XPO - expected BEGINNODE but found FILETYPE

rated by 0 users
2 Followers
1 Reply |
This post has 1 verified answer |

This question is answered

on 17 Feb 2012 8:41 AM

I have two instances (STATIC and TEST). I created TEST from STATIC. I made some programing changes to a project in TEST and export it to .XPO. I then try to import the .XPO into STATIC. I'm getting:

Error in line 15: expected BEGINNODE but found FILETYPE

I've inspected the exported .XPO and nothing seems malformed. All BEGINNODES and FILETYPE statements are where they should be.

It seems after about 3 or 4 tries, everything ends up importing w/out error.

Any ideas?

Ax2012 version 6.0.947.280

Thanks!

Verified Answer

Posted by Bill 'Luther' Thompson

replied on 17 Feb 2012 12:31 PM

Verified by Joe Courtney

Verified Answer

Hello,

This is a known issue and was recently fixed in a hotfix. If you contact your local support agency and request the hotfix for KB 2661360 you can get the fix that will allow the XPO files to be created correctly.

You can fix xpo files that have been created with this issue. The “Project” portion of the XPO gets created missing a keyword “ProjectNode”. This means that you get this error when you try to re-import:

Error in line 15: expected BEGINNODE but found FILETYPE

Bad:

ENDPROPERTIES

PROJECTCLASS

BEGINNODE

Good:

ENDPROPERTIES

PROJECTCLASS ProjectNode

BEGINNODE

All you need to do is add ProjectNode in the xpo file (opened in a text editor) to fix the xpo.

Best Regards,

Bill Thompson

Dynamics AX - Dynamics Sure Step - Online Support Engineer

============================================================

When responding to posts, please 'Reply to Group' via your newsreader so that

others may learn and benefit from your issue.

============================================================

This posting is provided 'AS IS' with no warranties, and confers no rights.

============================================================

rated by 0 users