I tried to install today’s beta. I received an eSellerate error (-2003). I followed the fix-it information and deleted the MindVision directory. Still broken. I did not go beyond.
Regular Scrivener works just fine, but having deleted the MindVision directory it had to re-activate for my computer.
So, the problem is not the permissions.
Jennifer had this, too, and I believe she is chasing it up with eSellerate. I’ve tested it on a couple of computers and have had no problems, and Ioa has done the same, so it must be computer-specific. The new update incorporates an update to the eSellerate framework, so it will try to install this eSellerate update. For some reason, it seems that on your machine, it is refusing to allow eSellerate to update. I’ll ask Jennifer to post back here after she has spoken to eSellerate.
Out of interest, is this on an admin or non-admin account?
(Incidentally, this should be posted in the Beta forums seeing as it is related to the current beta and not the release version.)
Hi Keith,
Same problem here, eSellerate error 2003; I went through the Fix instructions on Base knowledge page, and nothing worked - I’ve sent a mail to the address in the page with the “Stats.txt” file attached. Still my Scrivener copy it’s in “Try” version, unable to identify my license number.
Sorry for posting here, but I saw the post topic and thought, I’m not the only with this problem 
Waiting (without panic) for help…
Giovanni
Remember that you can roll back to the release version if you can’t open Scrivener at all. -2003 just means that there was an error installing the eSellerate engine. Jennifer has emailed eSellerate, so hopefully we’ll have some news before the holidays. 
I’ve just installed the beta in my user account and get the same problem. However if instead of clicking fix you just click OK when the error msg appears, Scrivener then loads in trial mode.
I’m guessing the beta will expire prior to the expiration of the trial period by which time the problem may be resolved.
Guys, I’m off on holiday tomorrow for two weeks, so it’s unlikely this is going to be resolved for another fortnight. If it’s stopping you from working, please revert to the non-beta version. Jennifer will post back here when she hears back from eSellerate.
I would definitely check the permissions on your user accounts as specified in the “Fix” information, if you haven’t already.
All the best,
Keith
I have checked ALL permissions with Disk Utility and Onyx, I don’t know if there are other steps to go in order to do this… As Tacitus said, I’ve got Scrivener working in trial mode (22 days remaining) - just in case, to re-install the ‘official’ release version, we need only to download and replace last beta? Just in case, you know 8)
Thanks, and enjoy your holidays Keith (and Ioa, David and all the L&L gang).
All the best,
Giovanni
Yes, just reinstalling the previous beta or the official release will get you running again; if you’ve tried fixing the permissions by following the steps on our support page, Scrivener will need to re-activate when you do this, but that should just take a second and then you’ll be off and running. I’ve contacted eSellerate support for help with this issue and will let you all know what I hear back when we get this resolved.
OK, troops, to fix the eSellerate permissions, please try the following:
Uninstall the latest Scrivener beta (build 21968) by dragging it from your Applications folder to the Trash
In the Finder, browse to the system level /Library/Frameworks folder (i.e. not the one in your home folder but the one you access by clicking on the main hard drive in the top of the left-hand source list in the Finder).
Delete the item named EWSMac.framework from the Frameworks folder by dragging it to your Trash and then emptying the Trash.
Go to ~/Library/Frameworks and delete the EWSMac.framework file from there (on Lion and up, the user Library is hidden; you can navigate to it by opening the Go menu and holding the Option key, then select “Library” when it appears in the menu)
Reinstall the Scrivener beta
Let us know if you’re still having trouble after those steps, but hopefully that will resolve the issue and get you running with the new beta.
Minor correction for Mtn Lion, at least: It’s the Go menu where the Library appears when you hold down option.
Bah, right you are. Fixed that.
Hi,
I followed these steps, reinstalled Scrivener (build 21968) and I’m now working just as usual, no more eSellerate errors.
Many thanks, guys (and girls )
And Merry Christmas & Happy New Year / Buon Natale & Buon Anno!
Giovanni
Worked fine on both of my Macs. Many thanks!
I’m just going to stick with the standard Scrivener for now. I have no pressing need for anything fancier and will wait till the ‘revised standard’ version comes out.
At any rate, thanks for the directions to correct it, if I change my mind.
Happy New Year to all
Don
Hi Don,
You’ll have the same problem in the standard version when the update is released, so you’ll need to fix it sooner or later anyway.
Happy New Year!
Keith
Keith -
Add me to the list of people with this problem and the latest Beta. I’ve used prior Betas without any problems, and after unsuccessfully working through every single step in the Troubleshooting page (*), I have been able to successfully revert to the current release.
(*) Among other things, I’m an engineer and have been using computers for literally decades. The troubleshooting steps were followed TO THE LETTER and did not resolve the issue. Something is seriously FUBAR’d with eSellerate.
LameLefty - eSellerate’s libraries have been updated between the current release and this beta; it will affect anyone with a certain configuration, and there is nothing we at L&L can do to affect that, so this isn’t something that will change when the beta becomes an official release. Switching back to the old version just switches back to using the old libraries, avoiding the problem in that way. Did you try working through the steps supplied earlier in this thread? That fix was provided by eSellerate and has worked for everyone with this issue:
Jennifer - Thank you for your patience in addressing this issue. I now have the current Beta version running properly. I have literally no idea what I did differently from last week as compared to this afternoon. I am generally very meticulous in troubleshooting and testing - I am currently beta testing software and prototype hardware for several large companies in formal test programs and have done so for many years. I am quite perplexed, since I went through these same steps last week and it just didn’t work.
I’m also a bit chagrined that my first post was a complaint and my second is to eat crow. Mmmm . . . tasty, tasty crow.
I tried to run the beta, but it kept asking for my registration number.
I purchased my Mac version of Scrivener from the App Store, and have no Mac registration number.
I do have one for the windows version which i use at work (my other job).
And yes, I purchased two copies, three when the ipad version is available.
Any thoughts on installing the beta?
writing occurs everywhere.
Wm.
It’s possible to do this, it just needs a little set up. There are detailed instructions here.
Thanks for supporting Scrivener in all its incarnations! 