Aperture won't start up (cannot access this library)

When I try to open Aperture I am getting a message straight away saying:
*Aperture cannot access this library*
+To use this library, make sure its file permissions are set correctly.+
I cannot find a way to do this. I have restored the disk permissions but that hasn't helped.
Any help would be greatly appreciated.
Chris

Thanks for the help guys.
I had already done the Get Info idea with no luck.
I ran the Consistency Check for a good 24 hours, in which time it never got above 75% and didn't seem to be doing much. Following other forum posts I quit that and ran the 'Rebuild Library' function from the same menu. After an hour or so this seemed to have done the trick and the program had launched. I then did Consistency Check as well to be on the safe side, which it did a lot faster. Everything now seems good.
Thanks again.
Chris

Similar Messages

Error Message - "Aperture cannot access this library"

I'm using OS 10.5.7 and Aperture 2.1.3. I recently had an error message pop-up when I try to start Aperture that says, "Aperture cannot access this library. To use this library, make sure its file permissions are set correctly." Unfortunately, I can't seem to open up my library. Any ideas how to fix this or what is wrong? Thanks

Hello,
attached I would like to report how the problem solved.
1. I had 63 Minute Call to Apple Support and we are tring some things. Finally I Spend spend 1 day for testing.
2. Testing procedure:
A) I exported each project step by step
B) Than I deleted all appr. 50 projects in Aperture Library.
C) After that I Imported each project to Aperture back.
Result: 2 Project was corrupted, one of it was going well after export/import procedure how ever but the second ones error was constant appearing if I try to import it. The project consisting of 512 jpg files in total appr. 500MB.
The solution for this project:
I moved this jpg´s to waste bin und imported it from waste bin to Aperture again into a new project. Than I tested it again(Export/import) and it was fine.
For final check I delete my Aperture backup und start a new one.
Than start a compleate restoring from that last backup.
Every thing was fine, all project include albums or books are ok.
The pictures in the corrupted project was not imported by Aperture, they was created on a PC system(XP). Maybe that was the reason for the problem.
A friend sad, that windows use not the agreed standard for jpg´s.
I don´t know. So I´m happy all my books are back that is imported for a wedding photographer.
Have fun
bernhard66

HT1941 I have inadvertently changed a file permission setting. When opening Aperture I get the following; Aperture cannot access this library. To use this library make sure it's file permissions are set correctly. I am an old dude new to Mac OS. What up?

I have inadvertently changed a file permission setting. When opening Aperture I get the following; "Aperture cannot access this library. To use this library make sure it's file permissions are set correctly". I am an old dude new to Mac OS. Looked in settings but have no idea how to allow file sharing to myself. I have been using Aperture actively for 6 weeks. I'm the only one using this Mac. What up?

Back up all data now.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. You can demote it back to standard status when this step has been completed.
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Drag or copy — do not type — the following line into the Terminal window, then press return:
sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:20 ~ $_ ; chmod -R -N ~ $_ 2> /dev/null
Be sure to select the whole line by triple-clicking anywhere in it. You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. You don't need to post the warning. If you don’t have a login password, you’ll need to set one before you can run the command.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2
Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.
When the OS X Utilities screen appears, select Utilities ▹ Terminal from the menu bar. A text window opens.
In the Terminal window, type this:
resetpassword
That's one word with no spaces. Then press return. A Reset Password window opens. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select  ▹ Restart from the menu bar.

The hard drive on my MacBookPro crashed. The Apple store replaced it. Since then I can't open iphoto. It asks to rebuild library; when I click yes, I get: "Aperture cannot access this library; reset permissions." I don't own Aperture!

The hard drive on my MacBookPro recently crashed. The Apple store replaced it. Since then I can't open iphoto. It asks to rebuild library; when I click yes, I get: "Aperture cannot access this library; reset permissions." I don't own Aperture! Any thoughts on how I can rebuild the iphoto library? Currently I can't even get into it.

Back up all data. Don't continue unless you're sure you can restore from a backup, even if you're unable to log in.
This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.
Step 1
If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.
Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):
{ sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -R $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null
Launch the Terminal application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.
Paste into the Terminal window (command-V). You'll be prompted for your login password. Nothing will be displayed when you type it. You may get a one-time warning to be careful. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.
The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.
Step 2 (optional)
Take this step only if you have trouble with Step 1 or if it doesn't solve the problem.
Boot into Recovery. When the OS X Utilities screen appears, select
Utilities ▹ Terminal
from the menu bar. A Terminal window will open.
In the Terminal window, type this:
res
Press the tab key. The partial command you typed will automatically be completed to this:
resetpassword
Press return. A Reset Password window will open. You’re not going to reset a password.
Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.
Select your username from the menu labeled Select the user account if not already selected.
Under Reset Home Directory Permissions and ACLs, click the Reset button.
Select
 ▹ Restart
from the menu bar.

Aperture cannot access this library" followed by "To use this library, make sure its file permissions are set correctly."

Hi,
I am completely confused. I use aperture everyday and today when I tried to open it I got the following message " aperture cannot access this library" then it said to use this library , make sure its file permissions are set correctly"
So i read a bunch of posts and opened aperture while holding down option and command and repaired the file permissions. it did nothing, when I tried to open aperture I received the same message. So then i tried opening it while holding down just the option key. This brought up all of my libraries but when I chose the library i use daily the same message came up.
Does anyone know how to fix this and/ or why it is happening?
Thank you

No idea how to check the format, not familiar with Drobo products. Does the drive show up in Disk Utility? If so you should be able to see how it is formatted there.
How long has this setup been in use?
Aperture libraries have to be on locally connected drives formatted as OS Extended as per Apple (see Format external drives to Mac OS Extended before using with Aperture for example). While Aperture may work with other setups there is always the possibility that the library will become unusable at any point in time with no warning.
Try to find out the format of the drive and post back. Maybe something can be done but from the error messages you are getting I'm thinking the best course of action will be to restore from backups onto a correctly formatted drive.
regards

"Aperture Cannot Access This Library"

Hi folks,
I have 8 or so libraries on a USB-connected drive and 1 library on my internal iMac drive.
When I run Aperture, it opens the latter fine, but when I attempt to switch libraries, I get the Subject error along with a message to check permissions.
Permissions on the former are identical to the latter.
I have tried OPT-COMMAND opening Aperture to attempt a file-permission repair, but that only works against the latter library - the one that's ok. I.e., there's no option to ask it to repair other libraries that are not the current one it knows about.
Any suggestions welcome.
Thanks

When I run Aperture, it opens the latter fine, but when I attempt to switch libraries, I get the Subject error along with a message to check permissions.
Please post the exact error message.
How is the USB drive formatted? You can see the formatting in the "File > Get Info" panel, if you select the drive in the Finder. The format should be "Mac OS X (Journaled)" extended.
Also set the "Ignore Ownership on this volume" flag.
Can you open the Aperture libraries in question, if you drag them from your external drive to your internal disk?
Regards
Léonie

Aperture cannot access this library, aperture cannot access this library

I received this message today when I tried to open the aperture 3. The library is on an external LaCie hard disk plugged into the imac

Andrew,
are you the owner of the files on your LaCie drive? If not, I'd try to reset the owner:
First check your current user id: Open a Terminal window:
Enter:
    echo $UID
On my system this will print : 502
Then check the UID associated with your La Cie files:
Enter into the Terminal window:
   ls -an
then add a "space", then drag the icon of your La Cie drive from the Finder to the Terminal, to enter the path to the drive, hit "return".
This should print listing similar to this: and the second column should correspond to your UID.
bash-3.2$ ls -an /Volumes/HermioneMedia
total 41240
drwxrwxr-x@ 45      502 20      1598 5 Aug 09:43 .
drwxrwxrwt@ 5      0    80       170 11 Aug 16:09 ..
-rw-rw-r--   1      502 20      6148 11 Aug 14:04 .DS_Store
d--x--x--x   8      502 20       272 29 Jul 10:55 .DocumentRevisions-V100
drwx------   5      502 20       170 5 Mai 16:53 .Spotlight-V100
drwxrwxrwt@ 5      502 20       170 28 Jul 15:31 .TemporaryItems
d-wx-wx-wt   3      502 20       102 11 Aug 16:09 .Trashes
If you see a different number, try to change the ownership:
Type:
sudo chown -R $UID
then again add a "space", then drag the icon of your La Cie drive from the Finder to the Terminal, to enter the path to the drive, hit "return". You will have to authorize as administrator, so double check what you typed. This will set the user id of all files on your drive to your own user id.
Regards
Léonie
PS: you may want to look in the Mountain Lion Forum as well, for example:
Permissions problem - unable to write to external drive
there seems to be a similar problem discussed, and I hope we will see answers there soon.

HT3805 I recently upgraded to mavericks on iMac . now when i open aperture I get the message"aperture cannot access this library. to use this library, make sure its file permissions are set correctly" I have repaid permissions via the aperture first aid.

I repaired the permissions in aperture first aid. I notice my short user name has changed from the one before the mavericks upgrade.

I notice my short user name has changed from the one before the mavericks upgrade.
Then you created a new user account when upgrading. How did you upgrade? Did erase the system and set up your mac completely new? If your short user name has changed, you are no longer the owner of your Aperture library, if it ha been created with your old user name.
I repaired the permissions in aperture first aid.
And after repairing the permissions you can still not access it?
Where is the library located? On an external drive or in your Home folder?

Help! Upgraded to 3.2. I receive this message, "Aperture cannot access this library."

How can I possibly make changes if Aperture doesn't launch?

Have you tried to see if you can run the Troubleshooting Basics?

Thread safety bug in XPS Serializer or FixedDocument sequence? "calling thread cannot access this object..."

Every once in a while (500 iterations or more) I'm getting an exception in the static method below stating "calling thread cannot access this object because a different thread owns it". Thing is, this method references no external objects
and performs no special threading operations. All of the WPF objects are created and consumed in this method. The only aspect that is multi-threaded is that this method can get called concurrently on different threads in the same app domain (the
project is a Windows service). That said the fileToDecollate parameter will be unique every time, so there is no "collision" as far as that goes.
Any ideas?   This is maddening and in theory it should not be possible to blow this error.
Exception Information------------------------------------------
System.InvalidOperationException: The calling thread cannot access this object because a different thread owns it.
   at System.Windows.Threading.Dispatcher.VerifyAccess()
   at System.Windows.DependencyObject.GetLocalValueEnumerator()
   at System.Windows.Xps.Serialization.SerializersCacheManager.GetTypeDependencyPropertiesCacheItem(Object serializableObject)
   at System.Windows.Xps.Serialization.SerializersCacheManager.GetSerializableDependencyProperties(Object serializableObject)
   at System.Windows.Xps.Serialization.SerializablePropertyCollection.InitializeSerializableDependencyProperties()
   at System.Windows.Xps.Serialization.SerializablePropertyCollection.Initialize(PackageSerializationManager serializationManager, Object targetObject)
   at System.Windows.Xps.Serialization.SerializableObjectContext.CreateContext(PackageSerializationManager serializationManager, Object serializableObject, SerializableObjectContext serializableObjectParentContext, SerializablePropertyContext serializablePropertyContext)
   at System.Windows.Xps.Serialization.ReachSerializer.DiscoverObjectData(Object serializedObject, SerializablePropertyContext serializedProperty)
   at System.Windows.Xps.Serialization.ReachSerializer.SerializeObject(Object serializedObject)
   at System.Windows.Xps.Serialization.FixedDocumentSerializer.SerializeObject(Object serializedObject)
   at System.Windows.Xps.Serialization.ReachDocumentReferenceSerializer.PersistObjectData(SerializableObjectContext serializableObjectContext)
   at System.Windows.Xps.Serialization.ReachSerializer.SerializeObject(Object serializedObject)
   at System.Windows.Xps.Serialization.ReachDocumentReferenceCollectionSerializer.SerializeDocumentReference(Object documentReference)
   at System.Windows.Xps.Serialization.ReachDocumentReferenceCollectionSerializer.SerializeDocumentReferences(SerializableObjectContext serializableObjectContext)
   at System.Windows.Xps.Serialization.ReachDocumentReferenceCollectionSerializer.PersistObjectData(SerializableObjectContext serializableObjectContext)
   at System.Windows.Xps.Serialization.ReachSerializer.SerializeObject(SerializablePropertyContext serializedProperty)
   at System.Windows.Xps.Serialization.ReachSerializer.SerializeProperty(SerializablePropertyContext serializablePropertyContext)
   at System.Windows.Xps.Serialization.ReachSerializer.SerializeProperties(SerializableObjectContext serializableObjectContext)
   at System.Windows.Xps.Serialization.ReachSerializer.SerializeObjectCore(SerializableObjectContext serializableObjectContext)
   at System.Windows.Xps.Serialization.DocumentSequenceSerializer.PersistObjectData(SerializableObjectContext serializableObjectContext)
   at System.Windows.Xps.Serialization.ReachSerializer.SerializeObject(Object serializedObject)
   at System.Windows.Xps.Serialization.XpsSerializationManager.SaveAsXaml(Object serializedObject)
   at System.Windows.Xps.XpsDocumentWriter.SaveAsXaml(Object serializedObject, Boolean isSync)
   at System.Windows.Xps.XpsDocumentWriter.Write(FixedDocumentSequence fixedDocumentSequence)
   at MyCompany.Utilities.Document.XPSDocument.Decollate(String fileToDecollate, String outputPath) in E:\Projects\MyCompany\Utilities\MyCompany.Utilities.Document\XPSDocument.cs:line 358
   at MyCompany.Services.ERM.XPSCapture.Decollate(String fileToDecollate, String outputPath) in E:\Projects\MyCompany\Services\MyCompany.Services.ERM\XPSCapture.cs:line 210
   at MyCompany.Services.ERM.ERMFileProcessor.decollateERMFile(String tempERMFile, IFileCapture fileCapture) in E:\Projects\MyCompany\Services\MyCompany.Services.ERM\ERMFileProcessor.cs:line 1257
   at MyCompany.Services.ERM.ERMFileProcessor.process() in E:\Projects\doc-link\MyCompany\Services\Altec.Services.ERM\ERMFileProcessor.cs:line 354
   at MyCompany.Services.ERM.ERMFileProcessor.Process(ProcessingCompleteCallback callback) in E:\Projects\MyCompany\Services\MyCompany.Services.ERM\ERMFileProcessor.cs:line 90
Additonal Info------------------------------------------
ExceptionManager.MachineName: BTP-30-DEV
ExceptionManager.WindowsIdentity: XXXXX-WA\Bradley
ExceptionManager.FullName: WindowsBase, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
ExceptionManager.AppDomainName: MyCompany.XXXXXXServiceHost.exe
ExceptionManager.ProcessInfo: PID=7392, ThreadID=7816, Managed ThreadID=36, Name=MyCompany.XXXXXXServiceHost, Uptime=00:02:12.2548416
ExceptionManager.ProcessResourceUsage: Working Set=265188 KB, Peak Working Set=525940 KB, Virtual Memory Size=530264 KB, Peak VM Size=809832 KB, Handles=631
ExceptionManager.SystemMemory: Load=81%, Total Physical=3168748 KB, Free Physical=586736 KB, Total PageFile=5213700
publicstaticList<string>
Decollate(stringfileToDecollate,
stringoutputPath)
// iterate fixed documents and fixed pages, create new XPS files
List<string>
xpsDecFiles = newList<string>();
using(XpsDocumentxpsSourceDocument
= newXpsDocument(fileToDecollate,
FileAccess.Read))
    FixedDocumentSequencefixedDocSeq
= xpsSourceDocument.GetFixedDocumentSequence();
    intpageNumber = 0;
    foreach(DocumentReferencedocReference
infixedDocSeq.References)
      FixedDocumentsourceFixedDoc
= docReference.GetDocument(false);
      foreach(PageContentpage
insourceFixedDoc.Pages)
        pageNumber++;
        // prepare new fixed doc sequence
FixedDocumentSequencenewFixedDocSeq
= new
FixedDocumentSequence();
DocumentReferencenewDocReference
= new
DocumentReference();
FixedDocumentnewFdoc
= new
FixedDocument();
newDocReference.SetDocument(newFdoc);
// copy the page
PageContentnewPage =
new
PageContent();
newPage.Source = page.Source;
(newPage asIUriContext).BaseUri
= ((IUriContext)page).BaseUri;
// tickle this method... presumably just to load the FixedPage data.
FixedPagenewFixedPage
= newPage.GetPageRoot(false);
// Add page to fixed doc sequence.
newFdoc.Pages.Add(newPage);
// Always do this last: add document reference to fixed doc sequence.
newFixedDocSeq.References.Add(newDocReference);
// create and save new XPS doc
stringdecFileName =
Path.Combine(outputPath,
Path.GetFileNameWithoutExtension(fileToDecollate)
+ "~"+ (pageNumber).ToString()
+ FileExtensions.XPS);
if(File.Exists(decFileName))
File.Delete(decFileName);
XpsDocumentnewXPSDoc
= new
XpsDocument(decFileName,
FileAccess.ReadWrite);
// testing. thread IDs should be the same.
//Debug.Assert(System.Windows.Threading.Dispatcher.CurrentDispatcher.Thread.ManagedThreadId == newFixedDocSeq.Dispatcher.Thread.ManagedThreadId);
XpsDocument.CreateXpsDocumentWriter(newXPSDoc).Write(newFixedDocSeq);
newXPSDoc.Close();
// add file to list
xpsDecFiles.Add(decFileName);
returnxpsDecFiles;

I have opened a support case with Microsoft through my employer. I'm convinced there is some .NET framework code that is not thread safe. I did put together a test harness app that demonstrates the problem (within 30 seconds or so after
you start it) and I sent that to MS support. They're looking into it. Anyone else who is curious can download the sample project here:
https://skydrive.live.com/redir?resid=5CBB4B55BCCB2D67!443&authkey=!AGEnR3CKrXUU6E0
Bradley
Bradley P.

Aperture won't start unless connected to my Vault USB Drive

Hello All,
I have a 17" MBP runing aperture. My Aperture won't start unless the USB drive containig the vault is connected. Anyone having the same issue? Any remedy to this?

Try holding the option key down whilst clicking on the Aperture icon in the dock and choosing your library this way.
Tony

The version of GroupWise you are using cannot access this post office

I built a new Server and added it to my PCSD Tree. The new server name is
GroupWise and has an IP Address of 10.10.0.13.
I followed the GroupWise 7 Installation Guide and installed GroupWise to
this server. At no point did I find any place to enter the GroupWise
License.
During the install I discovered that 4 of my long time employees were not
able to be assigned to this new GroupWise server. It appears that a one
time (Long time ago) these 4 employees were part of an old GroupWise Mail
server that must have been removed. I can not find any reference to this
old GroupWise server. My thought is to delete the accounts for there 4
users and recreate the accounts.
However the larger problem is this: I can not login to the GroupWise
Server. Below are two screen shots of what I’m getting when I
launch the GroupWise 7 Client. When I look at the .NLM loaded on the
Server for GroupWise MTA 7.0 it shows Domain Total=1 Closed=0, Post
Offices Total=1 Closed=1, Gateways Total=0 Closed=0.
On the Client, when I launch GroupWise, The Novell GroupWise Startup has a
message in the message window “The version of GroupWise you are
using cannot access this post office”. Then after clicking OK three
times, the following message appears on the screen “GroupWise did
not initialize successfully, Please run GroupWise Setup, or contact your
system administrator. Unspecified error OLE Error 80004005

*During the install I discovered that 4 of my long time employees were not
able to be assigned to this new GroupWise server. It appears that a one
time (Long time ago) these 4 employees were part of an old GroupWise Mail
server that must have been removed. I can not find any reference to this
old GroupWise server. My thought is to delete the accounts for there 4
users and recreate the accounts.
**You need to disassociate these four NDS users from any GW attributes.
Right-click each user in C1, GroupWise Utilities->GW / eDirectory
Association->Disassociate GroupWise Attributes.
*** When I do as instructed I get the following error:
[username] is missing the following attribute: NGW: Post Office
~~~~~~~~~~~~~~~~~~~~~~~~
*GroupWise MTA 7.0 it shows Domain Total=1 Closed=0, Post
Offices Total=1 Closed=1, Gateways Total=0 Closed=0.
**If the post office is closed, you need to determine why this is. On the
MTA, hit F10, Configuration Status, highlight your PO and hit enter,
select details, then look at the last closure reason.
*** Last Closure Reason= Missing or incomplete address information
[ When I installed GroupWise, I wanted all the e-mail to be stored on the
EMAIL Volume. During the install, I Changed the Install Directory to
\Groupwiseemail. After the install I have two directories in this volume.
One called DOMAIN and the other called PCAM (PCAM is name of my domain).
~~~~~~~~~~~~~~~~~~~~~~~~
*On the Client, when I launch GroupWise, The Novell GroupWise Startup has
a message in the message window 'The version of GroupWise you are
using cannot access this post office'.
**What version of GroupWise is on the server and what version client are
you
using? Also, if you pull up the properties of both the domain and post
office in C1 what is the database version listed as?
*** I installed GroupWise 7 both Server and Client. I'm thinking this is
due to the Post Office being closed. I only have 1 Post Office.
Thank You;
Lewis

VO extensions error -- You cannot access this draft quote( very Urgent)

Hi Oaf experts,
I have a requirement ,Two custom fields is to be added into a standard page,The new 2 fields are not avaialbe in standard table,there are no attribute columns are available in standard table
my functional consultant told that to create a custom table for the additional 2 fields,
so i have created a custom table for that 2 fields and cretaed an EO based on that table,
Based on EO i have extended VO.
after extending VO,deploying,bouncing the page is giving an error like 'You cannot access this draft quote'.
can any body help on this to reslove this issue
or gvie me an idea to add new fields in a standard page, In the case of the fields are in custom table.
Thanks in advance,
Edited by: user12260892 on Jan 12, 2010 6:17 AM

Hi Benjamin,
Thnx for your reply.
I have checked the source system for the external system. Actually it is a BW Qual system and the client copy from BW Prod has been done. So when they have done the client copy, the SS in the SS tab is that of R/3 Prod and not the R/3 Qual. But when I mentioned that this might be the reason, the client says even though it's showing as R/3 prod, in SM59 the SS is R/3 qual only.
But I am not sure whether this is correct or not and how to go about solving this???
And is it like even though we do Client copy and then replicate it, it will take from the SS that is in SM59 or the thing which is available in SS tab in RSA1???
InfoObjects seem to be fine.
Master data has been loaded.
Check definition of the RemoteCube - What do I exactly check in the definition, any specific thing???
If not there could be an issue with the BAPI - How to check whether there is any issue with BAPI???

VO extensions error : ' You cannot access this draft quote '

Hi Oaf Experts,
After extending VO iam getting one error in the page ' You cannot access this draft quote ', by removing the vo extension the error is going,but the error is not related my VO, it is a Standard Error.
can anybody help on this issue.
thanks in advance.
Edited by: user12260892 on Jan 14, 2010 4:44 AM

OK. So this is an ongoing problem and has been for over 1 month. The only way I could submit a payment is using paypal. I tried a mastercard and Visa - neither worked. Use paypal or transfer a bank payment - that is your best chance of updating it. Apparently their technicians are working very hard to fix this but it's still not working. Changing web browsers, computers etc don't work. Good luck. It's taken me 3 weeks to finally give up and use paypal.

I have problem in signing in I don't like read and accept terms I cannot access this I don't know about this read and accept terms this is poor, I just like android's simple option and simple singing in, but how to use apple I'd?

I have problem in signing in I don't like read and accept terms I cannot access this I don't know about this read and accept terms this is poor, I just like android's simple option and simple singing in, but how to use apple I'd?

Your computer is called an iMac.
Did you turn proxies on? If so, you should turn them off.

Aperture won't start up (cannot access this library)

Similar Messages

Maybe you are looking for