I have been getting this error for about 4 months now and was ignoring it because Poser seemed to work fine with it. I decided it was time to re-install a fresh copy of Poser and clean it up. Everything was fine until I pointed Poser to my old runtime folder for PP2010 and now the error pops up every time I start Poser and it looks into my runtimes. I have Poser set so the PP2014 runtime is in the Poser folder on the C Drive and my old PP2010 runtime is on another drive. Any idea what this could be?

Is your old runtime in the c:/Program Files hierarchy? I've noticed that then I run Poser the dates of the external; runtime folders change, so something must be written to them. If it's under Program Files, UAC will object to writing in those folders...

PP2014 runtime is in C:/program but my old PP2010 runtime is in J:/runtime 2010. I'll see if running the program as administrator fixes the problem.

OK, running as admin doesn't help.

Change the word runtime to anything else but runtimexxx

Hi there

Please have look on this thread over on RDNA

http://forum.runtimedna.com/showthread.php?75445-Error-code-after-Poser-Pro-2012-lock-up-while-rendering

Hope this helps

Thanks,Jura

Jules: actually the old runtime folder is labeled "Runtime" and is in J:/Poser Pro 2010/Runtime. I changed the name of the runtime folder to "ALLPOSERSTUFF," and Poser gave me an error that that was not a valid Poser runtime folder. I switched it back to Runtime and Poser opens it up but still gives me that error message when it does.

Jura: thanks for the link. That guy had exactly the same problem and came to pretty much the same conclusion that the error wasn't preventing him from using the program but it was annoying hem. They were unable to figure out what the cause was.

Poser needs the name runtime but not in the foldername above so you should create something like oldposer/runtime/. IMO this will solve your problem.

Jules53757 posted at 4:16PM Fri, 09 October 2015 - #4233019

Poser needs the name runtime but not in the foldername above so you should create something like oldposer/runtime/. IMO this will solve your problem.

Cool, I'll try that right now.

EDIT: changed the name of the old poser folder from Poser Pro 2010 to "Old Poser" but the problem still exists.

Hi there

Can you try edit yours Runtimes via Text editor or Notepad? Runtime LibraryPrefs is located C:UsersYourNameAppDataRoamingPoser Pro10

I would at least try have look on this and check if there is something which can cause this,personally I've all my runtimes on second HDD with one big folder which is called in my case as Poser Runtimes and there I've several runtimes like Poser Pro 2014 stock runtime,then my custom ones like V4,V3,clothes etc and Genesis stuff

As per above linked thread over on RDNA I would think this can be caused Python scripts,I would at least try remove or put yours pythons on desktop for now and run Poser Pro if you will be getting this error or I would put offending Runtime from Poser Pro location on desktop too and test again

Hope this helps and good luck

Thanks,Jura

[ghostship2]...

Jura: thanks for the link. That guy had exactly the same problem and came to pretty much the same conclusion that the error wasn't preventing him from using the program but it was annoying hem. They were unable to figure out what the cause was.

I took a brief scan of that thread.

First, make sure that Poser has all the permissions that it needs. Right-click on the Poser .exe file, go to Properties, then Compatibility, then choose Always Run in Administrator Mode. (Win7, your OS may differ.) Poser may need this in order to access files/locations outside of its own directory structure or to run scripted operations.

Sometimes, certain Wacros/python scripts are referenced in Poser's menus and it looks for them, but can't find them if it has a runtime mismatch. ie: "Orphaned" Python scripts in an external runtime end up looking for elements, but have the wrong directory references. The old solution was to simply make sure to install all python scripts and apps that depended upon them to both the program's native runtime and the external runtime. Then, it was hoped, Poser or the script would eventually figure it out and find whatever they needed.. What wacros/pythons/scripts do you have that might be susceptible to this? Reinstall/update or try the old shadow-copy fooling method and just install them to both runtimes.

Deleting your preferences files is easy and painless and doesn't really cause you any inconvenience other than having to reset them the way you wish. It's a good "catch all" solution for simple problems. It's possible there could be some runtime conflicts there, so just go ahead and delete them or back them up and then delete them. Instructions, here: https://support.smithmicro.com/customer/portal/articles/1982174-solving-weird-issues-with-poser-by-removing-the-preferences

Troubleshooting those three things successfully "should" clear up the problem, I would think.

I know this is an old thread, but I had the same problem and found the solution(at least for me). In my case, in my character folder there was a shortcut to the same folder. I was moving folder around and it must have been created by accident. When I deleted the shortcut, Poser no longer gives me that error.

I've just broken a PZ3 with this error.

It was not even an external run-time, but an FBX freebie import. Well behaved, too !! Single rig, 100% original scale, Yay !!

When I found a dozen-plus more such ports by same author --HiGuys920 at DA-- I gathered them all into their own Windows' sub-folder. Which, of course, broke the hard-set paths in that PZ3...

My bad.