A typical NOTEID: NT0000XXXX
A typical UNID: UNID: 4107F5F69B159A3771EF373572C7DEAE
Example: "Error validating user [user name] while processing calendar appointment (NoteID: NT000021AE) in <path to user's mail database.nsf>: Can't find user in Name and Address Book"
Example: "Unable to store document in NotesServerName <path to database.nsf> (NoteID = 1528610) from NotesUserName HD:Data:mail:USERMAIL.NSF (NoteID = 31714): Network operation did not complete in a reasonable amount of time; please retry"
There are several ways you can find a Notes document referred to in an error message with the document's Universal Note ID (UNID) or NoteID. The Domino Administrator client provides an option to search by the Universal Note ID (UNID) or Note ID. Open the Files tab in the Admin client, and look for "Find Note" under the Tools Databases drop-down on the right side of the screen) which can locate documents and design elements based on the NoteID. The input parameter requires typing the Hexadecimal version of the NoteID. Type the last four characters from the Note ID number. If the NoteID appears in Decimal Format, use a calculator to find the Hexadecimal equivalent and enter that number as the NoteID. Note: It is possible to create a view of documents by their NoteIDs. Instructions for doing this are noted below. In this dialogue box you can also search by the Universal Note ID or (UNID)
If you do not have access to a Domino Administrator client, use one of the following methods:
A. Download NotesPeek and use the feature to open a Note by NoteID. This can be done by highlighting a database in NotesPeek and selecting Data Open Note.
B. You can use the @NoteID function to build a sorted view of NoteID numbers. Instructions are below. Note that this will locate only documents. For example, if you are attempting to locate a design element such as a view or form, use one of the utilities mentioned above.
How to Build a View in a Database for Finding a Notes Document with its NoteID (To be performed by a Domino Developer)
There are two approaches to building this view.
Approach #1: Build a view that lists the documents by their Hexadecimal value
1. Build a view and place the @NoteID function in the first column; sort the column.
This will return the Hexadecimal format of the NoteID. This will give you a column that begin with the characters "NT".
For example:
NoteID
NT001752CE
NT001752DA
NT00175322
NT00175326
...
2. Convert the NoteID number from the error message which is a DECIMAL value into its HEXADECIMAL equivalent.
You can use the Windows Calculator program (CALC.EXE) to do this. In Calculator's menu, select View, Scientific. Select the radio button labeled 'Dec' (DECIMAL), and then enter the error number, such as 1528610. Next, select the radio button labeled 'Hex' (HEXADECIMAL). The display will change to show you the hexadecimal equivalent of the number you entered, for example: 175322.
Other suggestions:
- Build a Notes view which displays the Note IDs (Hex) so that they will match the format that they are displayed in error messages (Dec).
or
- Most spreadsheet programs offer a formula for converting decimal values to hexadecimal.
or
- Use a scientific calculator.
3. Locate the Notes document by finding the hexadecimal number in the NoteID view you built.
For example:
NoteID
NT001752CE
NT001752DA
NT00175322
Approach #2: Build a view that lists the documents by their Decimal value
Create a view with this formula in the first Sorted Column:
First:=@Middle(@NoteID;9;1);
FirstN:=@TextToNumber(@If(First="A";"10";First="B";"11";First="C";"12";First="D";"13";First="E";"14";First="F";"15";First));
Second:=@Middle(@NoteID;8;1);
SecondN:=@TextToNumber(@If(Second="A";"10";Second="B";"11";Second="C";"12";Second="D";"13";Second="E";"14";Second="F";"15";Second));
Third:=@Middle(@NoteID;7;1);
ThirdN:=@TextToNumber(@If(Third="A";"10";Third="B";"11";Third="C";"12";Third="D";"13";Third="E";"14";Third="F";"15";Third));
Fourth:=@Middle(@NoteID;6;1);
FourthN:=@TextToNumber(@If(Fourth="A";"10";Fourth="B";"11";Fourth="C";"12";Fourth="D";"13";Fourth="E";"14";Fourth="F";"15";Fourth));
Fifth:=@Middle(@NoteID;5;1);
FifthN:=@TextToNumber(@If(Fifth="A";"10";Fifth="B";"11";Fifth="C";"12";Fifth="D";"13";Fifth="E";"14";Fifth="F";"15";Fifth));
Sixth:=@Middle(@NoteID;4;1);
SixthN:=@TextToNumber(@If(Sixth="A";"10";Sixth="B";"11";Sixth="C";"12";Sixth="D";"13";Sixth="E";"14";Sixth="F";"15";Sixth));
Seventh:=@Middle(@NoteID;3;1);
SeventhN:=@TextToNumber(@If(Seventh="A";"10";Seventh="B";"11";Seventh="C";"12";Seventh="D";"13";Seventh="E";"14";Seventh="F";"15";Seventh));
ID:=((SeventhN*@Power(16 ;6))+(SixthN*@Power(16 ;5))+(FifthN*@Power(16 ;4))+(FourthN*@Power(16 ;3))+(ThirdN*@Power(16 ;2))+(SecondN*@Power(16 ;1 ))+FirstN*@Power(16;0));
ID
© 2024 Quest Software Inc. ALL RIGHTS RESERVED. Terms of Use Privacy Cookie Preference Center