Invalid License Code
After a change of configuration of the disks in my desktop computer, I found that CaptureOne, as it tends to do at such times, made my activation invalid.
No problem - I just went to the 'My account' section of the PhaseOne website and deactivated all activations so that I would have an activation with which to re-activate CaptureOne 6.4.3 Pro (64 bit) on my computer.
This done, I re-activated CaptureOne Pro on my laptop computer - no problem.
But when I try to re-activate CaptureOne on my desktop machine - the computer that originally had the issue, as soon as I enter the license code as shown below (note the license code shown is NOT my license code - but produces the same results):
IMAGE DELETED BY ADMINISTRATOR: Your personal product key is showing.
I have tried uninstalling (using the full uninstall procedure details in the knowledge base) and then reinstalling - no joy.
I have tried repairing the .net runtime - still no joy.
I have also tried installing and activating the 32bit version of CaptureOne 6.4.3. This activates fine using the same license code.
My machine specs are:
Processor: I7-2700K
Memory: 16GB DDR3 (4x4GB)
Disk: WD Velociraptor 1TB
OS: Win7 64Bit.
Can anyone help. I have already raised a support case - but it's the weekend and no-one has replied.
I really don't want to start again with a clean Windows install if I can help it at this time.
Wade Oram
No problem - I just went to the 'My account' section of the PhaseOne website and deactivated all activations so that I would have an activation with which to re-activate CaptureOne 6.4.3 Pro (64 bit) on my computer.
This done, I re-activated CaptureOne Pro on my laptop computer - no problem.
But when I try to re-activate CaptureOne on my desktop machine - the computer that originally had the issue, as soon as I enter the license code as shown below (note the license code shown is NOT my license code - but produces the same results):
IMAGE DELETED BY ADMINISTRATOR: Your personal product key is showing.
I have tried uninstalling (using the full uninstall procedure details in the knowledge base) and then reinstalling - no joy.
I have tried repairing the .net runtime - still no joy.
I have also tried installing and activating the 32bit version of CaptureOne 6.4.3. This activates fine using the same license code.
My machine specs are:
Processor: I7-2700K
Memory: 16GB DDR3 (4x4GB)
Disk: WD Velociraptor 1TB
OS: Win7 64Bit.
Can anyone help. I have already raised a support case - but it's the weekend and no-one has replied.
I really don't want to start again with a clean Windows install if I can help it at this time.
Wade Oram
1
-
My best "clean" uninstalls have been done with the free version of Revo uninstall.
http://www.revouninstaller.com/revo_uni ... nload.html
That, followed by ccleaner to clean the registry of any leftovers should work for you.
http://www.piriform.com/CCLEANER
Be careful with this one, as I recall it wants to load other toolbars as well.
Good luck,
Jim0 -
Still no progress.
I've installed the 32-bit version for now. So I'm not desperate - at least until I get frustrated with the memory issues on 32-bit.
Wade.0 -
The license file might get in the way. I have seen similar issues after disk replacements. I posted a solution here:
viewtopic.php?p=53080#p53080
Scroll dowwn to my 2 Jan 2012 post.
Use it at your own risk. Deactivate your 32-bit activation first. Let us know if it helped.0 -
I'm afraid that this did not fix my issue.
I've now had a reply from PhaseOne support staff so I shall be persuing that for a while.
Wade.0 -
Just an update for anyone who may be interested.
PhaseOne support staff asked me to install an older version of CaptureOne 64-bit (6.4.1) and see it that worked OK. It did not.
They also supplied a small diagnostic app and asked me to run it and send the output back to them - which I did. Apparently, it did not show anything wrong since they have now asked for a full system info report and they are suggesting that 'something may have changed in Windows' since they have another similar case from someone else.
In the meantime, they suggest that I continue to use the 32-bit version of CaptureOne Pro while they investigate further.
Ironic really since it was the 'out of memory' issues with the 32bit version of CaptureOne Pro that caused me to install the 64bit version of Windows 7 in the first place. ☹️
Wade.0 -
FWIW,
I run C1 V6 latest Windows release on an elderly Dual Core Pentium based Dell machine with 32Bit Win 7 and 3Gb RAM available. I used to get "out of memory" type errors on this machine with V5 but not recently with V6.
I can run 2 or 3 sessions of C1 in separate windows and have Processing going on in the background without running out of memory even when running other applications at the same time. The machine has 2 x 1Gb conventional drives installed and, at the moment, both are rather full (again). Most processing is done solely on the C drive.
My CPU usage widget often shows both cores working at 100% but memory availability, these days, rarely drops below 800Mb free.
I will admit that this is a dedicated machine and only has photo editor programs and Internet Explorer installed plus a handful of utilities. No Adobe products on this machine, not even the PDF reader.
If I can get away with my system spec. I think you should probably expect to have yours working with 32 bit (albeit it with Win 64 bit?) without too many problems unless you are doing something extreme. Huge files? Do you by any chance use TIFFs?
Grant0 -
Using the 32 bit version of CaptureOne Pro V6.x, I can provoke an 'out of memory' error very easily using the keystone correction tools amongst others.
I have received an update from PhaseOne. The issue is due to the fact that I have the .Net 4.5 beta installed on my system.
They suggested that this could be because of a 'Windows 8' installation (persumably into the same file system). However, in my case that is not how it came about. I have .Net 4.5 beta because I have installed the beta version of MS VisualStudio 11.
Wade.0 -
Incidentally, I noticed that PhoneOne staff have been a little bit overeager and removed the screen capture from my original posting - they obviously did not read the bit where I explicitely stated "this is NOT my license code".
Wade0 -
[quote="Wade" wrote:
Using the 32 bit version of CaptureOne Pro V6.x, I can provoke an 'out of memory' error very easily using the keystone correction tools amongst others.
Interesting. Not a feature I have used often and I don't recall any problems when I did. However, now you have mentioned it I will try to remember to play around and see what happens. Better to understand any potential problems in advance of possible use than to discover them when in a hurry!
Grant0 -
Going off topic now - but this was one very reliable way of provoking on out of memory error on CaptureOne 6.2.1 (I haven't been looking for the fault in later revisions and I have been running 64bit for some time now): - I copied three Canon 5D Raw images to a separate folder (with none of the associated .cos or .cop files).
- I then ran Capture One with the default session and used the library tool to navigate to the new folder with the three images.
- I then applied a (different) keystone correction to each of the three in turn without making any other adjustments.
- I then selected the second of the three images. The preview image appeared quickly and sharp.
- I then selected the first image. The preview appeared unsharp and remained that way until a number of "out of memory : please restart the application" popup windows appeared.
Wade0 -
Just to follow up on Wade's issue.
The cause has been identified as a change in Windows .Net 4.5, this will not effect everyone that installs .Net 4.5 but it certainly has the potential to cause conflict with the Activation system. We've made a fix for this and will introduce it with the next update. Anyone having this issue should contact support for an immediate solution.0 -
An update to address this issue is now available;
http://www.phaseone.com/en/Downloads/CaptureOne.aspx0
Post ist für Kommentare geschlossen.
Kommentare
12 Kommentare