Community Expert

Answered

Error 205

Forum|Forum|4 years ago
July 20, 2021
15 replies
65249 views

Installed Substance Designer Painter, Stager

Stager runs fine,

Designer, Painter keep generating error 205 messages.

Have installed , uninstalled, rebooted, logged in to ACC, logged out.

No Joy.

I am signed into my ACC subscription. I have signed out. I have signed in, have signed out.

It appears that Substance app is not finding my subscription.

I cannot even sign in our out from the app. I keep getting the error code 205 popup.

Selecting the contact support brings up a 404 page error.

I have disabled my Anti-virus many times

I have tried different browsers.

Anyone? Anyone? Bueller???

How to

Correct answer Michael J. Hoffman

Hi jbm,

I had reported the same earlier:

https://community.adobe.com/t5/substance-3d-designer/issues-on-first-launch/td-p/12187180

I contacted customer care via chat and they gave me the solution right away (log out/in of the CC desktop app). Glad you got it sorted, too.

Show previous replies

D

D3K17

Participant

I was able to solve the error without the restart and just re-logging into ACC (quitting and reopening the application).

R

Ray-man

Participating Frequently

Had the same problem in Photoshop, error code 205. Logged out of the Creative Cloud desktop app and then logged back into Creative Cloud and it worked!

H

HarleyTDavis

Inspiring

I'm having the same problem, will try the fix suggested. If I may... ...a lot of app verification anymore is time sensitive, or more accurately, processor clock sensitive. Threading and application multitasking, especially with one app interfacing with another before performing the full operation, can be hazardous with new security measures in place like rootless and protected memory space. They really need to be in sync, and running in the same context (for permissions in processing, permissions in memory, and permissions in general). If they are not running in the proper context, or only one program is running in a particular process tree's context (this is usually numbered like interrupt queing), then they are not in sync. The file that is being accessed by the substance programs is actually in the files for CCDesktop. Unfortunately, on my system, the file cannot open from the substance apps. This file opens on every other app. Not the substance apps. It isn't an installation issue, per se, but it is a file that is a part of the fileset that the app needs in order to start up. When the apps are installed, there is a hash file set created (if it doesn't already exist) in your running user data (windows is appdata in your user folder, on mac, in user library), and it holds security values for your system and for the account in adobe CC. The hash file, if it already exists, is typically RUNNING in the background if you are logged in to CCDesktop, and it cannot be replaced with a new one. This is unfortunate, since a new hash must be generated to include the information for the new apps. IF the file is accessible (on my system, my system monitor shows the app attempting to access but failing), it may still be the old version, making the apps crash, as they believe you have a pirate copy. You can regenerate the hash by logging out, restarting, exit CCDesk if its running, then open it again and log in if needed. This should regenerate the hash file with the values necessary for the apps to run.

I don't work for adobe, but I watch my system carefully, and I have some understanding of recent techniques with software anti-piracy. The new Software as A Service model relies heavily on hashfiles and checksums to verify ownership over the internet. However, to make this less intrusive, many extra services, offered as part of the new software functionality where the services match common use of the software, are hosted online as file downloads, instructionals etc.

The safest route:

1. Log out of CCDesktop

2. Exit CCDesktop or kill the process

3. Reboot

4. Run or open CCDesktop

5. Log in from CCDesktop

6. Try software, if still bugged, uninstall, and repeat the process, then reinstall the apps, logout CCDesk, then back in again. If still bugged, try the standalone download installer. Sometimes antivirus or system security functions identify backend libraries (DLL files in windows or support files in mac\unix) as possible intrusions or virus, and disable the running context necessary for them to function correctly, when the installer isn't run from a standalone package.

Luca Giarrizzo

Community Manager

Hello Harley,

Thank you for bringing up your concerns in such detail! I have passed along your message to our team for awareness.

Best regards.

Luca Giarrizzo | Quality Engineer - Substance 3D Designer | Adobe

H

HarleyTDavis

Inspiring

I do consulting work on software suite and technology integration. Adobe is one of the key products I get questions about.

While the SAAS model has proven problematic in the startup, it has started to iron out. Here are some tips for your business users:

1. Do not auto update software

2. Do not update during regular business hours

3. Do not remove old versions until the new version has been working without incident for 2 weeks

4. Before updating: Backup the app folder in program files, backup the Appdata folder for each user on windows, and the user library application support, preferences, and other user library folders for each user on mac\*nix before you run the updates. This includes the CCDesktop folders. IF the updated software has issues, you can try to uninstall then reinstall, when that fails, Kill the CCDesktop process, replace the files and folders then reboot and reopen ccdesktop. You will have to replace ALL apps that you updated even the ones that had no problem. Update the others again, then repeat this before updating the erroneous software again.

5. If you update your Operating system, even by minor update, check CCDesktop for updates and follow step 4 to back up any apps that show an update pending.

6. Training in new capabilities or in using the same capabilities that have moved to other titles should be done as a two week learning session, followed by a couple of training tasks each week for 6 weeks, then a training task from any task they've learned with you, each week, randomized, with a report on any difficulties they had in completing it. Any tasks that don't happen often enough to be memorable for one employee can be relegated to those that do them often, and any tasks that don't happen often at all can be relegated to a single employee who should complete one of these each week. Only three learning tasks should be necessary for any single employee\user per week. This allows you to guage which work stages can be handled with how many employees, allowing you to split up work more efficiently. DO NOT HAVE USERS TRAIN THE SAME WEEK, always split departments or areas of users up. One user from each, maybe two if the team has 4 or more, should train on new capabilities at a time, over the course of a week, and at different times of the workday.