Hi
I have installed Photoshop CS5 on a coupel of comupters(XP) and I get following error when I start it. The user are useing mandatory porfiles NTUSER.MAN.
AppName:photoshop.exe AppVer: 12.0.1.0 ModName:scriptingsupport.8li
ModVer:10.0.0.0 Offset:000d183a
//Tobbe
I found this on adobe´s forum (
http://forums.adobe.com/message/3148825?tstart=0 ) --------->
It turns out that at least for Windows XP, Adobe CS5 doesn't like any form of mandatory user profile. So for example if like many places at work if you want to have user control so that they can't do too much with their user accounts, you give them a mandatory user profile so the look and feel is the same for everyone when they log in.
This is then often tied in to Windows Group Policies that control the account further. Microsoft Active Directory and Novell Zenworks 7/10 do this pretty well and in our old builds with XP SP3 and Adobe CS2 it all worked perfectly well.
If we were to rename the profile's registry file NTUSER.MAN to NTUSER.DAT and make no further changes whatsoever, all of CS5 Design Standard's apps run. The moment it's named back to NTUSER.MAN (with no changes whatsoever made to the mandatory user profile!) we get the same launch errors as mentioned for the Design Standard applications as mentioned in this thread. Exactly the same ones.
Whether CS5 or its Service Manager application is looking at the user's profile during launch, it's a pretty poor show. Even with all the CS5 updates, exactly the same errors occur.
We don't want to give the users any form of higher level rights when launching the apps either, as otherwise they can press the "Deactivate" button and deactivate CS5 on the machine (and I'm sure I'm not alone in this).
In short, Adobe needs to realise that there are plenty of companies and institutions who need to lock down their users and allow them to run the software functionally with a mandatory user profile. It's worked in the past, and needs to work now.
Any tip for me?
//Tobias
We don't want to give the users any form of higher level rights when launching the apps either, as otherwise they can press the "Deactivate" button and deactivate CS5 on the machine (and I'm sure I'm not alone in this).
I'm not the best authority on this, but I believe you can suppress this by using the Adobe deployment toolkit. If the serial is hard-coded in the deployment package and flagged accordingly, these options will never even show up anywhere....
Mylenium
I found this in your forum.
Go to<drive>:\Program Files\Adobe\Adobe Photoshop CS5 (64bit)\Plug-ins\Extensions\ (or CS4 - depending on version)
Locate File:
ScriptingSupport.8li
Disable this extension by renaming the file with a tilde in front of the file name. Thus:
~ScriptingSupport.8li
Start Photoshop - it works and is mainly functional.
That´s seams to solve the startup problem, but what about all functions? Is there any patch for this?
//Tobbe
Hi,
I am having exactly the same issue here with CS5 Photoshop and mandatory profiles. Couldn't get the product to start without errors so I renamed the scriptingsupport.8li file and that solved the startup problems. However the reduction in functionality is unacceptable.
Removed the mandatory profile from a single domain user and tested Photoshop and everything is wonderful. SO what's the solution Adobe? Are you going to fix this or do I have to take all my users off mandatory profiles. I don't think either are going to happen certainly not the latter.
What gauls me the most is the amount of money that we paid for the site license for a product that doesn't work in a not unusual scenario and isn't going to be fixed.
Regards
One unhappy bunny.
Found this after narrowing down my crashing cs5 to a problem with "ScriptingSupport.8li"
I'm using Win7 64bit with CS5 12.0.2 x64 and i was able to re-active scripting support after changing the compatibility mode to "Windows Vista".
I have no idea why but maybe it helps someone else...
Regards
B.
I just corrected the problem last night based on some obscure posting. I tried updating Video Drivers, alter BIOS settings, turned off AV, you name it. It came down to a conflict with my account on my XP machine. I created a new account with admin rights, and volia, it worked perfectly, including my plug-ins (Nik and OnONE), I could not afford the 'disable' workaround as it killed my access to these apps. Try it out. If it does not work, you can always delete the account.
I'm having the same problem. I am a computer teacher and when I log in with Admin, no problems. When the students log in, the computers will lock up for a couple minutes at a time randomly. No real pattern to it. I can't believe that Adobe isn't on this. I have older machines, running XP, so it would be nice to abandon CS5, but I only have a license for Photoshop 6. I have a 5-machine license for CS2 but they won't give me a lab license for it even though we spend big money to buy a site license for CS5.
Any ideas on how to allow my students to use Photoshop 12x? I even tried updating to CS 5.5 and no luck.
I've tried the first set of suggestions on the Adobe web site including:
Updating Windows XP
Updating Photoshop
Re-creating preferences
Update video driver
I have no plug ins
No extensions
Chris, there is a new user reporting an issue with mandatory profiles on the french U2U: http://forums.adobe.com/thread/948264 He also has to remove scriptingsupport.8li
Hi,
We were getting similar errors after installing Adobe Creative Suite CS5.5 Design Premium on Windows XP Professional SP3 and attempting to run the software as a standard user in the 'Domain Guests' group:
Adobe Dreamweaver CS5.5
Application starts but immediately closes shortly afterwards
Adobe Flash Professional CS5.5
Application crashes on startup and displays the following errors:
'Adobe Flash CS5.5 has encountered a problem and needs to close. We are sorry for the inconvenience.'
Error signature:
AppName: flash.exe AppVer: 11.5.1.349 ModName: flbridge.dll
ModVer: 9.0.0.0 Offset: 000162d0
Adobe Illustrator CS5.1
Application displays the following error on startup:
Adobe Illustrator
-----------------
Error loading plugins.
AISaveForWeb.aip
DxfDwg.aip
PNGFileFormat.aip
[ ] Don't Show Again
Adobe InDesign CS5.5
Application crashes on startup and displays the following errors:
'InDesign.exe has encountered a problem and needs to close. We are sorry for the inconvenience.'
Error signature:
AppName: indesign.exe AppVer: 7.5.2.318 ModName: support for javascript.rpln
ModVer: 7.5.0.142 Offset: 000361a8
Adobe Photoshop CS5.1
Application crashes on startup and displays the following errors:
'Adobe Photoshop CS5.1 has encountered a problem and needs to close. We are sorry for the inconvenience.'
Error signature:
AppName: photoshop.exe AppVer: 12.1.0.0 ModName: scriptingsupport.8li
ModVer: 10.0.0.0 Offset: 000d1a2e
In each of these cases, I found eventually that the problem was because the user account that I was testing with was a member of the 'Domain Guests' group on the domain. (Other posts online seem to indicate that the same problem may occur if accounts are set up to use mandatory profiles, a Windows domain feature). In every case removing the user from the Domain Guests group and then logging on again resolved the problem.
I have yet to find a workaround for this issue other than removing the user from the Domain Guests group which does not involve removing some of the functionality from this software. Indeed if you run the software as a member of the local 'Guests' group, you get an error stating that this is not supported.
However if Adobe would like to troubleshoot the problem, it may well be caused by a call to RSACryptoServiceProvider and/or CryptAcquireContext returning NTE_TEMPORARY_PROFILE, as described in the following MSDN blog post:
http://blogs.msdn.com/b/alejacma/archive/2007/10/23/rsacryptoservicepr ovider-fails-when-used-with-mandatory-profiles.aspx
It seems as if these API calls were not designed to be called in the context of a mandatory and/or temporary profile (such as that created for a Domain Guest user account), and so if Adobe need to use these calls in their programs, they need to handle the NTE_TEMPORARY_PROFILE error and work around it if possible. (Searching for 'NET_TEMPORARY_PROFILE' in Google brings up a few possibilities).
If you are trying to use the software in the mean time try removing your user account from the 'Domain Guests' group and see if this helps.
Recently I've begun to have Photoshop CS 5.04 crash upon starting up. Resetting the prefererence (CTRL+ALT+SHIFT), deleting the preferences file /users/appdata/roaming/.... neither solve the problem. I haven't done anything different to my PC, yet, I do plan on moving everything to a new HDD that hasn't been done yet, how can I fix this ?
Make sure your drivers are updated, check your event logs for errors and especially for evidence of any failing hardware.
If you suspect a software issue, restore your system back to a time when it was working well using the various Windows System Restore or Backup Restoral facilities.
-Noel
We had the same problem for some users on XP workstation, including Administrator. Although some users could launch Photoshop without any problem. It ends up that to fix it you need to rename/delete HKCU\Software\Adobe\IAC key. This key will be recreated next time user launches Photoshop.
North America
Europe, Middle East and Africa
Asia Pacific