This section covers the following topics:
If you have access to a password reset page, browse to that page and use it to reset your password. Otherwise, contact an Oracle IRM Server administrator for assistance.
Oracle IRM Desktop usually redirects you to a web page that provides contact details for the person who can give you the rights you need. Contact that person and explain which document you are trying to open, and why you need access to it. They will decide whether it is appropriate to give you any rights.
If you see a message saying that your rights are already checked out to another computer, you need to check in your rights from that computer, or wait for the rights to expire.
If you cannot connect to the server (Oracle IRM Server), there may be a problem with your network connection. If you connect to the Internet from a corporate network, you may need assistance from your network administrator to resolve the problem. Use the Oracle IRM Server Connection Test dialog to diagnose the problem. (Open this dialog from the Test link on the page that reported the error.)
If you see this message for only some documents, but can open others, then it is possible that you are being served by multiple Oracle IRM servers, one of which is temporarily unavailable.
Your rights have expired and you have been redirected to a web page.
If you are working offline, then go online and try to open the document again. It is possible that your locally cached rights have expired and that more rights can be obtained as soon as you go online.
If your rights have expired permanently, then the web page should provide contact details for the administrators who are authorized to grant you more rights.
If you were editing a sealed document online when your rights expired or were revoked, you will lose any unsaved changes. If your rights were downgraded, or if your locally cached rights expired, you are given an opportunity to save changes.
This is rare, but it is possible that your rights have been reduced since you started working on the document. If you think this might be the case, contact the owner of the context to which the document is sealed.
It is quite usual for documents to be sealed to different contexts even if they come from the same originator. For example, you might receive documents sealed to a "Company Confidential" context and others sealed to a "Board Matters" context. It is likely that your rights for these two contexts will be different, such that you can only open one, or you can open them both, but edit only one.
As a security measure, the Oracle IRM Server administrator has configured an account lock-out policy that prevents anyone from trying to guess passwords. If your account has been locked out, it is possible that someone else has been trying to log in using your account. Depending on the lock-out policy, your account might become accessible again after a short period, or might need to be manually reset. Contact your Oracle IRM Server administrator for further information.
The purpose of sealing documents is to control who has access, and who has edit rights. Edit rights are fine-grained, so you might find that you cannot use all of the Microsoft Office features you are familiar with. For example, you might find that you cannot print a sealed document, or that you are prevented from pasting information from one sealed document to another, or that the track changes option is always on.
Oracle IRM's goal is that using sealed documents should be very similar to using unsealed documents, if you have the necessary set of rights. Where rights are granted, you should be able to do what you usually do in most cases. In some cases, the need to protect a document might mean that options you are familiar with need to be disabled because they provide security loopholes.
See "Using Sealed Email". To use sealed email to full advantage, you need to enable email integration in Oracle IRM Desktop.
To maintain the security of the VB code, it is not possible to save your VB code changes directly in the sealed document.
Use the following procedure to save changes that you have made to VB code in a sealed document:
Select the container document for the VB code document that you have changed.
Select Save in the container document.