Post

8 followers Follow
2
Avatar

Mag+ production tool: better error message for "error 1009"

When creating my first test issue with the production tool, and saving the issue, I got the error: 'And unhandled error has occurred: Type.Error: Error #1009"

Probably due to the fact that I did not add a brand in the brand settings editor, because when I did - I could save the issue.

Maybe a good idea to give a more understandable error message (or field validation)?

 

thanks!

Martijn Berk

Please sign in to leave a comment.

30 comments

0
Avatar

Yeah, my production tool keeps crashing and giving me error #3001. No idea if it's something I am doing wrong or not.

Bruce nuffer 0 votes
Comment actions Permalink
0
Avatar

my production keep crashing even though i add  a brand in the brand settings editor. (and no matter what im trying to do it keeps crashing!) - error 1009

i dont know what to do..  plz help.

 

Ester Sror 0 votes
Comment actions Permalink
0
Avatar

Hi, I'm having the same issue.. I just tried to reinstall everything and I've also deleted the Production Tool preferences but the tool keeps crashing with error #1009. Any idea?

Andrea

Andrea Cima 0 votes
Comment actions Permalink
0
Avatar

Hello Andrea,

Does the entire production tool crash & shut down or is it just giving you this error & nothing happens?

If it is completely crashing, can you obtain a crash log for us:

http://serato.com/scratchlive/support/6600/how-to-get-a-crash-log-in-mac-osx

Otherwise, this error code would indicate that the permissions on the folder you're exporting to are locked or read only.  Try right clicking on that folder, "Get Info" & look at the permissions.

Regards,

Mike Rettew 

Mag+ Support Team

Mike Rettew 0 votes
Comment actions Permalink
0
Avatar

Hi Mike,

The entire production tool crash right after I close the error. Attached one of the crash logs..

Thanks! Andrea

Andrea Cima 0 votes
Comment actions Permalink
0
Avatar

Andrea,

This error is most likely being thrown because you do not have "write" access to one or more of the files in your preferences folder or the folder(s) you are trying to export to.  Make sure that the folder & all sub-folders you that contain your preferences & where you are exporting to have "write" access & not just "read" access.

Regards,

Mike Rettew 

Mag+ Support Team

Mike Rettew 0 votes
Comment actions Permalink
0
Avatar

Hi Mike,

I've double-checked the permissions and everything is Read & write, both the folder/files I'm exporting too and the two folders/files in preferences. Besides, I've tried to install the software on another mac and on a win and I get the same issue on all of them...

Thanks, Andrea

 

Andrea Cima 0 votes
Comment actions Permalink
0
Avatar

Andrea,

Take a look at my screen shot & see if you have an IP address input into this section of the Production Tool

Screen_Shot_2013-09-13_at_11.17.36_AM.png

Mike Rettew 0 votes
Comment actions Permalink
0
Avatar

Hi Mike, I do have the input field for an IP address but it's not been set.. should it be set to something?

Thanks, Andrea

Andrea Cima 0 votes
Comment actions Permalink
0
Avatar

@Andrea. Yes, you need to add the IP address of your iPad. You can find it in the Mag+ Reviewer in 'User Settings'. It's the IP address given after 'Push Service:'

nathan 0 votes
Comment actions Permalink
0
Avatar

how we should do in Windows? Always crash and can't continue!!!!! Even unstall and reinstall can't solve this problem! Crazing

alex zhu 0 votes
Comment actions Permalink
0
Avatar

Alex,

It should work the same way in Windows.  Make sure you have the IP address from the target device entered in your Production Tool Preferences tab as stated above.

Regards,

Mike Rettew 

Mag+ Support Team

Mike Rettew 0 votes
Comment actions Permalink
0
Avatar

At least once a week when I open the production tool it'll open on the Error #1009 and force close the program before I have a chance to update the push address or anything (our wifi shifts often). Then I have to go through this whole process of resetting everything (deleting and reinstalling) in the production tool and creating a new brand and a new magplus settings file.

Is there a way to save me the hassle of this 20 minute endeavour? I'm not sure why it keeps doing this sporadically. 

 

Samantha 0 votes
Comment actions Permalink
0
Avatar

Yes - as well as deleting the indesign plugins/javascript. I'll get it working then build and send out sample mib files for the whole week just fine - then turn on the computer Monday morning to build and set up the new updated files and get the error again. I transfer the indesign files to and from my home computer (using an external hardrive) copy and replacing files in and out of the applications folder. I never do any production tool stuff at home though - just indesign. Would that be affecting the error?

Samantha 0 votes
Comment actions Permalink
0
Avatar

When you say you transfer the files to & from your computer, are you moving any of the .xml files associated with the Production Tool as well?

Could you send over a screenshot of your Preferences tab from within the Production Tool?

Regards,

Mike Rettew 

Mag+ Support Team

Mike Rettew 0 votes
Comment actions Permalink
0
Avatar

Not usually. Do you mean this tab? That might be it, to save time I'd copy over the whole Issues folder back and forth with all the exported verticals and such. 

Samantha 0 votes
Comment actions Permalink
0
Avatar

I was able to successfully export an android mib but now when I open the production tool it either does the 1009 error or the multi-device is blank and I can't load any verticals. I deleted and re-exported all the ipad verticals fresh from indesign. I feel like I spend more time fixing Mag+ glitches than actually designing. 

Do you have an email I can communicate with you directly?

Samantha 0 votes
Comment actions Permalink
0
Avatar

I'm having an interesting issue with the Mag+ Production Tool, the tool opens but fails to display any of the text labels within the tool.

I've deleted and reinstllaed both app and prefs. Screen shot attached.

I'm running OS 10.6.8 

 

Cate Holst 0 votes
Comment actions Permalink
0
Avatar

@Samatha, I will go ahead & open up a private support ticket with you.

@Cate, this could possibly be a system font conflict.  If you have a font management program with several of the same versions of fonts activated, try disabling some of these fonts & restart your Production Tool.

Regards,

Mike Rettew 

Mag+ Support Team

Mike Rettew 0 votes
Comment actions Permalink
0
Avatar

I got the answer to this one. 

The problem is you haven't selected the device to push to, so it;s failing.

In the production tool.

Click on the Preferences tab.

MIB Push Address: [ Enter your device address ]

Save.

That's it! At least it was for me.

Edward Cortez 0 votes
Comment actions Permalink
0
Avatar

I'm working on my first Mag+ Issue. Today I was try to build it in the Production tool. Every time I save I get 2 error messages. One saying "An unhandled error has occured TypeError: Error #1009 An unhandled error has occured Yes / No" When I choose yes the app shuts down. When I choose No the app will give me another error message  saying : "Cannot lock issue for update" 

How do I fix this on a Windows PC?

Michiel van Dam 0 votes
Comment actions Permalink
0
Avatar

I'm trying to load my issue into the Mag+ Production Tool and it won't let me import more than two pages. When I go to import a new page it replaces a previous page.

Also, when I go to Preferences, no instructional text appears or any roll over information  (see screen shot) . I've reinstalled Product Tool several times now too.

Thanks

Cate Holst 0 votes
Comment actions Permalink
0
Avatar

Hello Cate,

For the first issue, make sure you are using unique Vertical ID's within each of your verticals.  This is input in the Plugin.

For the fonts not appearing, that could be related to some system font conflicts on your computer.  If you are using a font management application, make sure you do not have any duplicate system fonts activated.

Regards,

Mike Rettew 

Mag+ Support Team

Mike Rettew 0 votes
Comment actions Permalink