Brand new year, brand new computer, brand new windows 8 pro, brand new Acad 2013 and brand new Carlson 2013. Eveything seems to work fine except I can't get Carlson to complete installation, what I get is :Error No. 0x8000FFFF, "Catasrophic Failure"
Anyone have any ideas, suggestions or expierences with this?
Possibly a bad disc?? If so, go to the Carlson website and download the latest 2013 version of your software and install from that .EXE file.
Tried that and got the same result...but thanks for your input
Time to call or email Carlson Support.
> Brand new year, brand new computer, brand new windows 8 pro, brand new Acad 2013 and brand new Carlson 2013. Eveything seems to work fine except I can't get Carlson to complete installation, what I get is :Error No. 0x8000FFFF, "Catasrophic Failure"
>
> Anyone have any ideas, suggestions or expierences with this?
At this time, I believe there is a problem with the installer program being used to deploy the product to 64-bit versions of Windows 8. As a result, Carlson does not officially support Windows 8 at the current time:
http://www.carlsonsw.com/support/system-requirement/
I am currently at a meeting with Dave Carlson and he indicated the Carlson development team has been working through the issue and an updated is expected very soon but I don't have any additional information at this time.
Back in my OLD programming days, 15 or so years ago, that particular code generally meant a file was not found.
Realizing that was a long time ago, I did a search (on bing) for "Error code 0x8000FFFF catastrophic failure". That number itself is -1 in decimal.
Apparently it now has many meanings.
I suspect it now takes a more general meaning in that "something" was not found or inaccessible.
Thinking about inaccessibility issues, I'll ask are logged as an administrator or does the account you are using have full admin rights? The installer may be trying to do something that needs those rights - like accessing the system folder or some particular registry keys, or perhaps simply updating/adding to the registry.
That code used to drive us nuts. Text returned with that exception would simply say "file not found" but zero indication about WHICH freakin file!! I've actually had it happen a couple of times in the last year or so and it's still a pain in the a$$ to debug.
Good luck.
E.