Authorization error when exporting business system

Hi ,
I am on XI 7.0 spo9.I am trying to transport from dev to qa .
I am able to easily export (login using xisuper ) Technical system.
However while exporting Business system .when it gives me to download a file I get an authorization error .
Kindly help

Hi,
Check XISUPER has the below roles in SU01.
SAP_BC_AI_LANDSCAPE_DB_RFC
SAP_SLD_ADMINISTRATOR
SAP_SLD_CONFIGURATOR
SAP_SLD_DEVELOPER
SAP_SLD_ORGANIZER
SAP_SLD_GUEST
add the above roles for XISUPER and get the green color those roles using Tcode : PFCG.
The above roles should be in green color.
Regards,
Venu.

Similar Messages

Error while assigning Business Systems in Integration Directory

Hi,
I'm getting an error when trying to assign the business systems in the integration directory.
The error i'm getting exactly is "access to object list of type BusinessSystem using the internalEOAService BusinesSystemAccessor failed " .
I've cleared the SLD_cache and checked it but the same error.
The business systems are appearing when i tried the transaction code SLD_CHECK and is in green status.
what might be the error.

Hey
just want to make sure,are u using communication channel with party or without party.
also make sure that user has sufficient authorizations
http://help.sap.com/saphelp_nw04/helpdata/en/c4/51104159ecef23e10000000a155106/content.htm
Thanx
Ahmad
Message was edited by:
Ahmad

Unable to Export Business System

Hi ,
I am on XI 7.0 spo9.I am trying to transport from dev to qa .
I am able to easily export (login using pisuper ) Technical system.
However while exporting Business system .when it gives me to download a file I get an error .I have the necessary authorisation
Kindly help

Hi,
First, you have to start the SLD.
To transport business you must first of all create business system groups, then associate the business systems with the group and finally map your business systems.
To create a group, proceed as follows:
> Business Systems
> Click on the drop-down next to Group and select Edit Groups
> Create a group for each environment (eg DEV, TST, PRD). Specify for each group which Integration Server is used.
To assign business systems to a group, proceed as follows:
> Business Systems (Group = all)
> Select your Business System
> Click on the Integration tab.
> Select the related Integration Server (which is associated with a group - see step 1)
To map your DEV Business Systems to TST Business Systems etc., proceed as follows:
> Business Systems
> Select the group of your choice
> Select your Business System
> Click on Transport
> Click on Add/Change Target
> Select the Target Group and System
KR, Danny De Roovere

Error when exporting reports using MAPI

We created a .NET class that wraps CR 2010 .NET Crystal Reports functions and made it COM visible. This class is used to create a COM object in a js script which in turn used to export reports to a PDF file with the destination MAPI.
It exports reports just fine without any errors however if prior to instantiation the exporting class we instantiate a class that has nothing to do with the Crystal Reports functions, our exporting object throws u201CExternal component has thrown an exception.u201D error when exporting. It appears that it has something to do with the SideBySide feature. I was wondering if somebody knows what causes this and if there is a way to fix this problem.
Thanks for your help!
 
 
Below are 2 procmon.exe outputs, the first when exporting works and the second when it doesnu2019t
 
 
 
1) Procmon.exe output when exporting works fine
 
 
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir SUCCESS Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL FAST IO DISALLOWED
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 7:16:30.7403615 AM test.exe 4396 FASTIO_QUERY_INFORMATION C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection:
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS SyncType: SyncTypeOther
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Image Base: 0x79260000, Image Size: 0x1073000
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryNameInformationFile, Name: \Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide\PreferExternalManifest NAME NOT FOUND Length: 20
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\SideBySide SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Generic Read, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 
 
 //////////////////////////////////////////////////////////////////////
 2) Procmon.exe output when exporting doesnu2019t work, notice that it tries to open MSO.dll at the same location as in the output above but fails, it tries then to open it at several other locations and fails
 
 
 HKLM\Software\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS Desired Access: Read
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS KeySetInformationClass: KeySetHandleTagsInformation, Length: 0
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\CommonFilesDir SUCCESS Type: REG_SZ, Length: 72, Data: C:\Program Files (x86)\Common Files
 HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL FAST IO DISALLOWED
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS Type: QueryBasicInformationFile, CreationTime: 9/17/2010 10:50:22 AM, LastAccessTime: 11/10/2010 5:47:02 PM, LastWriteTime: 9/17/2010 10:50:22 AM, ChangeTime: 2/17/2011 11:04:53 AM, FileAttributes: A
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\microsoft shared\OFFICE12\MSO.DLL SUCCESS Desired Access: Read Data/List Directory, Execute/Traverse, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a, OpenResult: Opened
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL FILE LOCKED WITH ONLY READERS SyncType: SyncTypeCreateSection, PageProtection:
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS SyncType: SyncTypeOther
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Program Files (x86)\Common Files\Microsoft Shared\OFFICE12\MSO.DLL SUCCESS
 C:\Users\Paul\projects\temp\test\Debug\MSO.dll FAST IO DISALLOWED
 C:\Users\Paul\projects\temp\test\Debug\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll FAST IO DISALLOWED
 C:\Program Files (x86)\Microsoft Office\Office12\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\SysWOW64\MSO.dll FAST IO DISALLOWED
 C:\Windows\SysWOW64\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\system\MSO.dll FAST IO DISALLOWED
 C:\Windows\system\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a
 C:\Windows\MSO.dll FAST IO DISALLOWED
 C:\Windows\MSO.dll NAME NOT FOUND Desired Access: Read Attributes, Disposition: Open, Options: Open Reparse Point, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

I tried to run exporting code in a .net application and got the same error. I first created the COM object that causes the problem and then ran exporting CR functions. It works fine if I run the code without creating the COM object.
Below is the code I used.
 Type objClassType = Type.GetTypeFromProgID("ebms.main");
 object objMain = Activator.CreateInstance(objClassType);
 try
 object[] p = new object[4];
 p[0] = "C:\\ebms\\co1";
 p[1] = "C:\\ebms\\co1";
 p[2] = "Administrator";
 p[3] = "";
 objClassType.InvokeMember("LoginToCompany", System.Reflection.BindingFlags.InvokeMethod, null, objMain, p);
 catch (Exception ex)
 this.RPTDoc = new ReportDocument();
 this.RPTDoc.Load(@"C:\\Users\\Paul\\Desktop\\AR Customer List.rpt");
 PdfRtfWordFormatOptions pdfOpts = ExportOptions.CreatePdfRtfWordFormatOptions();
 MicrosoftMailDestinationOptions mailOpts = ExportOptions.CreateMicrosoftMailDestinationOptions();
 ExportOptions exportOpts = new ExportOptions();
 pdfOpts.UsePageRange = false;
 exportOpts.ExportFormatOptions = pdfOpts;
 mailOpts.MailMessage = "something";
 mailOpts.MailSubject = "something";
 mailOpts.MailToList = "emailaddress";
 exportOpts.ExportDestinationOptions = mailOpts;
 exportOpts.ExportDestinationType = ExportDestinationType.MicrosoftMail;
 exportOpts.ExportFormatType = ExportFormatType.PortableDocFormat;
 try
 this.RPTDoc.Export(exportOpts);
 catch (Exception ex)
 MessageBox.Show(ex.Message, "Error", MessageBoxButtons.OK, MessageBoxIcon.Error);

Error when exporting file from LR5.2 - file created

After updating to LR5.2, I receive an error when exporting files to another disk drive. a file is created, but a warning appears "Unable to Export: "An internal error has occurred: Win32 API error 2 ("The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute". I also have CC iunstalled for other applications, but originally installed LR5 as a standalone Adobe application. I tried removing the program and reinstalling through CC, with no change in this behavior.

The answer is in the thread:
http://forums.adobe.com/thread/1303578?tstart=0

Error when exporting a pdf in SAP

She sends me the error when exporting a pdf from the SAP system, this is the message:
X Object reference not set to an instance of an object.
I hope I can support.
Annex image

See your other thread.

NO Authorization error when accessing Functional module RH_CUT_OBJECT

Hi,
I am getting NO AUTHORIZATIOn error when I am executing SE37-->FUNCTIONAL OBJECT-RH_CUT_OBJECT.
I also checked SU53 screenshot which says AUTHORIZATION CHECK SUCCESSFUL and there are no errors or missing authorizations highlighted in SU53.
I switched on the TRACE-ST01 then also the error is not captured.
I would like to know WHY am I getting NO AUTHORIZATION error.
I am already having access to T-CODE SE37, SE11, SE80, SMARTFORMS and authorization object S_DEVELOP.
I need to know this ASAP on why I am getting NO AUTHORIZATION error when I am trying to access the FUNCTIONAL MODULE RH_CUT_OBJECT whereas I am having all the required authorization required for ABAP Developer including SE37.
Is it something I need change at ABAP code level.
Please advise ASAP.

The reason is ..You do not have acess to see/acess the data this FM is trying to acess ...Debug the function module keep a breakpoint at The Raise statement see which authorization you do not have ....BTW this is my guess you are trying to demilit certain objects /infotypes using this FM and delimit basically makes that object non-usable in that system .So it is quite evident that every one will not have authorization for that .Please post in detail that what is it that you are trying to achieve using this function module .....
Also you can check with debugging which authority object is being checked before raising the message and can ask security team to get that added to your profile ....
Thanks,
Anjaneya

Procurement Coordinator received Authorization Error when creating Bid Inv

Hi All,
In SRM I have an issue Please help me in solving this. Please see below
Procurement Coordinator received Authorization Error when creating Bid Invitation from Sourcing Cockpit. Message states u201CMissing Transaction BBP_BID_EXTSOu201D; however Bid # is still created. User requests that Authorization issue is resolved and Bid # appear for Procurement Coordinators. This problem does not happen for Commodity Managers

Hi
Please do the following steps.
When you are using the Internal ITS,you need not run the report W3_PUBLISH_SERVICES.(only SIAC_PUBLISH_ALL_INT )
ALso pls check the foll:
-->activate the services through SICF tcode.
> Go to SICF transaction and activate the whole tree under the node Deafult host>sap>bc>gui>sap>its.
>Also maintain the settings in SE80>utilities>settings>internet transactuon server-->test service/Publish.
Table TWPURLSVR should have entries for the / SRM server line as well as gui and web server.
Could you please review again the following steps ?
Did you check that ICM was working correctly (TA SMICM) ?
1-Activate the necessary ICF services
With transaction SICF and locate the
services by path
/sap/public/bc/its/mimes
/sap/bc/gui/sap/its/webgui
2- Publish the IAC Services
With Transaction SE80 locate from
the menu Utilities -> Settings ->
Internet Transaction Server (Tab) ->
Publish (Tab) and set On Selected
Site = INTERNAL.
3- Locate the Internet Services SYSTEM and WEBGUI.
Publish these services with the Context
Menu -> Publish -> Complete Service
4- Browse to http://<server>:<icmport>/sap/bc/gui/
sap/its/webgui/! and login to the
webgui.
Hope this will help.
Please reward suitable points.
Regards
- Atul

Unknown error when exporting 32-bit 5.1 wav audio

I get the ever useful "Unknown error" when exporting the audio from Premiere Pro CS6 to a 32-bit, 5.1 channel uncompressed WAV file most of the time. I was able to get it to work just fine by pasting the audio to a new project, but that isn't working anymore. I get the same error when I change it to 24-bit audio. However, when I change to 16-bit sound it works fine.
First, is there a real audible difference between 16- and 32-bit when it's all going through a WAV to AC3 converter? The AC3 files get dumped into Encore as the audio track so that I can get 5.1 sound on blu-rays instead of Encore re-encoding things.
Second, what would cause it suddenly not work, and how can I get it working again?

That error can happen for many reasons...one of the reasons that I occassionaly get it is because I try exporting a movie to an external drive that has been formated in the old FAT32 instead of the NTSF standard. FAT32 only allows for file sizes up to 2 gigs. And as soon as it reaches that...I would get that error. I don't know if that is why you are getting that error...but it would be easy to check. 1) are you generating a file that is over 2 gigs? 2) is your drive that you are exporting to FAT 32 (just right click the drive in My Computer and select "properties" then just look for what it says next to "file system".

Error when exporting to hard-drive

Lightroom 4 was working fine before I tried to export to Flickr. The export was NOT successful, and after that, I encountered an error when exporting to hard drive. Although this error appears, the export to hard drive is always successuful. It is annoying to continuously receive this error message. Any help will be much appreciated. Thanks

That is the small trouble with screenshots: as unambiguous and helpful as they are they are hard to search for their content.
But it looks identical to several other posts here (http://forums.adobe.com/message/4341436#4341436, http://forums.adobe.com/message/4318154#4318154, http://forums.adobe.com/message/4285253#4285253, http://forums.adobe.com/message/4261252#4261252, http://forums.adobe.com/message/4177871#4177871):
In your export manager select "Do nothing" i.o. leaving it blank. down at the bottom where it asks for what to do in Post Processing After Export.
This should have the message go away.
For the sake of searchability I spell out the error message, so that others could find this being answered:
Unable to Export:
An internal error has occurred: Win32 API error 2 ("The system cannot find the file specified.") when calling ShellExecuteExW from AgWorkspace.shellExecute.
Cornelia

Error when exporting ABAP Programs and the Project

Hi All,
I keep on getting the following errors when I'm exporting the entire Project or only ABAP Programs (see attached screenshots).
- Screenshot 1 shows an error when exporting a Project.
- Screenshot 2 shows an error when exporting ABAP Program(s).
These errors occur in the DEV environment.
Please help.
Thank you all.
Kind regards,
Roli

Hi Ramakrishna,
I will send the log file for when exporting a project. However, the issue of exporting ABAP Programs is nor resolved.
In CMC we had to configure the system to Generate ABAP = True.
Thank you.
Kind regards,
Roli

'file could not be written due to an error' when exporting jpg

I'm working with an Illustrator file in CS2 and after a certain point it has started saying 'the file could not be written due to an error' when exporting to a jpg.
i've tried a couple things like deleting layers and although the file is much smaller, it still says the same error when exporting.
at its highest it was 130mb as an illustrator file and jpgs were 2-5mb.
i''ve tried copying some of the layers into a new file but the error report still comes when i'm exporting.
i have vector and raster based data in the file and tried turning off/deleting either of the layers and there is no difference.
i don't understand why it's started doing this because before it had no problem at all exporting before.
ANY IDEAS ANYONE? I'm trying not to have to reproduce days of work to remake the file.
many thanks,
P

Mylenium,
Sounds like you know a good deal about this product. Is there any way to restore a color profile/setting to an earlier point?
I don't recall changing it and to tell you the truth, wouldn't be able to say which it may have been set to before - if different.
Thanks,
Paul

Error when exporting to flat file in ODI 11g

This works ok in ODI 10g. I'm using IKM SQL to File Append on Windows Server 2008 R2
Getting the following error when exporting to a flat file in ODI 11g: ODI-40406: Bytes are too big for array
I've seen a couple of threads like this on the forum, but I've never seen an answer to the problem.

Problem is with the difference in behaviour for the IKM SQL to File Append KM between 10g and 11g.
Our 10g target file datastore had a mixture of fixed string and numeric columns. Mapping from the source to target was simple one to one column mapping. It generated the desired fixed format flat file; numerics were right adjusted with embedded decimal point and leading spaces. Each numeric column in the generated flat file occupied the exact space allocated to it in the layout. This gave the desired results, even though documentation for the 10g IKM states that all columns in the target must be string.
When we converted to 11g and tried to run this interface, it generated an error on the "numeric" columns because it was wrapping them in quotation marks. The result column was being treated as string, and it was larger than the defined target once it acquired those quotation marks.
In order to get 11g to work, I had to change all the numeric columns in the target data store to fixedstring 30. I then had to change the mapping for these numeric columns to convert them to right adjusted character strings (i.e. RIGHT(SPACE(30) + RTRIM(MyNumericColumn),30).
Now it works.

CIM_ERR_ALREADY_EXISTS: Error while creating Business System

Hi,
I am getting following error while creating Business System in SLD, the Technical System is already created from RZ70 transaction in the IDES system
Error Creating business system: CIM_ERR_ALREADY_EXISTS: Instance already exists://inbbssun01/sld/active:SAP_LogicalALESystem.CreattionClassName="SAP_LogicalALESystem", Name = "LSIDES800.SystemName.800.SystemName.IDS.SystemNumber.0020224902.SystemHome.idesecc"
Thanks,
RP

Hi,
This error means that a business system with this name(or associated with this technical system) is already there in SLD.
You need to check that before you try creating it (might be someone else have created it before)
Updated
If you have created and deleted a business system and then trying to recreate one then you need to delete all the instance of it from Content Management (in SLD)
Regards
Suraj
Edited by: S.R.Suraj on Nov 9, 2009 12:34 AM

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins?

In aperture 3.4.5, I get unsupported file error when exporting version of photo I've edited using plugins. I have try reinstalling aperture three times, deleting plists a few times, reinstalling plugins, restarting my MacBook Pro many times. Everything I've tried may fix the problem for a very short while and I can export a few photos before it returns. The problem happens with topaz and photomatrix pro plugins after I edited and try to export version.

I had the same problem with the Photomatix plug-in and this solved it for me. I realised it only happened with Photomatix and not other plug-ins so I checked where the plug-ins were installed. The Photomatix plug-in was installed in
~/Library/Application Support/Aperture/Plug-Ins/
where ~ is the home location for the current user account. All the other plug-ins however were installed in
Macintosh HD/Library/Application Support/Aperture/Plug-Ins/
which is the location that makes them available to all user accounts on your Mac. Moving the Photomatix plug-in to this location solved the problem for me.
Note that the Library directory under the first location is normally hidden, to get to it hold down the Option (Alt) key and select it from the Finder Go menu.

Authorization error when exporting business system

Similar Messages

Maybe you are looking for