Showing posts with label error. Show all posts
Showing posts with label error. Show all posts

Thursday, December 7, 2023

V14 Notes, Domino, Traveler are out Now

But your Notes install may have an issue.

NOTE: This post will be updated/edited as I figure out more of what is going on. Domino install-info after the Notes client info below.

I tried installing HCL notes, only comes in 64-bit now, on 2 different machines.

The installation was on top of the existing ones.

You may want to use the NICE tool to clean up the prior install first, might save you some headache.

1st is my usual laptop, 6 months old, Windows 11 Pro which already had 1202fp2(64-bit), and while it looked ok after about 20 minutes of waiting to finish, it gave me this, with no more details. It possibly happened while uninstalling or disabling something.


And then backed out the installation.

Subsequently, what I did was extracted the installer to a new location.
Then ran the setup, RunAs admin.
And this time it worked. Thank you Marc Thomas for the hint that there may be some extraction issue and to try it this way.
So, 2 clients installed, a server with traveler installed and it took about an hour and a half including troubleshooting/retries.


The 2nd installation on my Windows Server 2019 which is a hosted VM gave me this message:

And after trying again to click ok said this:


Never had something like this happen before during an install. 

I extracted the 1202 notes client as requested to get the MSI file and then the installation continued on its way. Also takes about 20 minutes.

So the Server install completed, even after asking for the 1202 code.

Now to figure out what is wrong with my Windows 11 install.

Domino Install

If you do a custom install, like I do, you will see the options to install Nomad and Ontime and I think Verse, my screen capture did not capture, sorry.

You will also see something my beta code did not do which is confirm the Domino login name for the startup services.

You may want to be careful with that if you don't know how you are logging in because your server may not start afterward.

Time to update was between 5-10 minutes including restarting the server and updating the Directory.

Traveler is also available and installs like usual in a few minutes.

Nomad works just like it did before, so the update did not change that, but it would be nice if it told us which version it was, instead of developer code which is 1.0.9.5525-3341. How do I know if mine was even updated? Maybe 1.0.9 was what was installed, but i already was at that level.

Verse works as well. 3.2, which I had installed, need to look up what version is installed as V14.

Ontime kept my configuration, and the booking settings still work as well.

Pretty cool when you think about all the stuff HC has to verify on the Domino side given these things are now included in the installation.

Friday, November 7, 2014

SnTT - In Which Port Settings Don't Quite Work

Been a long time since I wrote a Show n Tell Thursday so let's get on with it.

Building an IBM Domino cluster is not as difficult as it was years ago and I was done with the basic parts and wanted to test the fail over.

I figured easiest way to do this was to enter at a server console "stop port tcpip" while connected via rdp to the server.

I tested mail clients could fall over to the 2nd server and mail routed. Great.

Back to the server and server console and tell it to "start port tcpip".

I didn't think much about it and since there were some server updates to add to the box, I decided to shut it down after the updates were done.

It came back up and was running and I was working on another server in the domain when the client let me know no one could connect to the server. Odd, I was there and it "looked" ok. On closer inspection, it was not ok.

Errors that said databases could not be found, no route found, no network could be found, trace connections and some other fine error messages that mean nothing to the average person.

After poking around a bit, I figured the notes.ini needs to be edited. I checked with Rob Kirkland, of this book fame on Domino System Administration, and followed it to solve the problem.

I found the TCPIP port listed under disabled ports. Deleted it form there.
Found TCPIP=TCP,0,15,0,,45088 was missing which is for compression and encryption (see below).
Also missing was Ports=TCPIP

After putting it all back together, rebooted and all is good again. Still not sure why the commands failed and did not help this 8.5.3FixPack6 server but at least someone else out there will not have to waste an hour or 2 tying to figure it out.
Selection NOTES.INI parameter
          Nothing TCPIP=TCP,0,15,0,,12288,
Compression only TCPIP=TCP,0,15,0,,12320,
Encryption only TCPIP=TCP,0,15,0,,45056,
Both TCPIP=TCP,0,15,0,,45088,

EDITED: October 20, 2020 The below is pulled from the most awesome list of ini settings ever.

https://entwicklercamp.de/customer/notesini.nsf/85255a87005060c585255a850068ca6f/8d0f57b937909eefc1256e9e0045eddb?OpenDocument

Configuration for a TCPIP port.

Examples: TCPIP1=TCP,0,15,0,,12288

TCPIP=TCP, 0, 15, 0 [,,x] <----------- This is the setup for your TCP Port
.......|...|..|... Application Data buffer size (0 is default which = 8000)
.......|...|..Placeholder not used by TCP
.......|...Placeholder not used by TCP
.......This is the port driver name

The last parameter x ([,,x] above) can be decoded as follows:
0 X 8000 Encryption is enabled

0 X 0020 Compression is requested
0 X 4000 driver is internal
0 X 2000 no-op
0 X 1000 always for V2 and V3
0 X 0002 set to log modem I/O
0 X 0004 set to enable RTS/CTS


8020 which would be Encryption plus Compression is in hexadecimal code 45088

Selection NOTES.INI parameter
Nothing TCPIP=TCP,0,15,0,,12288,
Compression only TCPIP=TCP,0,15,0,,12320,
Encryption only TCPIP=TCP,0,15,0,,45056,
Both TCPIP=TCP,0,15,0,,45088,

Tuesday, July 23, 2013

SnTT - Traveler 9.0 IF1 In Case you get This Error

lotus hat, sntt
Sorry old picture, no new one for Tuesday.

While updating my IBM Domino server from 9.0 to 9.0HF328, I also saw an update for IBM Notes and Lotus Notes Traveler.

Just been busy and did not get to these yet and Domino and Notes went fine.

Traveler update however it seems was a corrupted download. Given it has been posted for 2 months I presume it is not IBM, but my download.

In any event, for those who like me end up seeing these messages after they ran the installer, which said it was done properly :

07/22/2013 08:28:52 PM  Notes Traveler: SEVERE *system Unable to open database C
 /IBM/Domino/data/traveler\map\CalMap.nsf.
07/22/2013 08:28:52 PM  Notes Traveler: SEVERE *system IBM Notes Traveler server
 could not be started.  The exception was com.lotus.sync.util.ComponentNotStarte
dException: Unable to open database C:/IBM/Domino/data/traveler\map\CalMap.nsf..
 Exception Thrown: com.lotus.sync.util.ComponentNotStartedException: Unable to o
 en database C:/IBM/Domino/data/traveler\map\CalMap.nsf.
07/22/2013 08:28:52 PM  Notes Traveler: SEVERE *system 14 records are pending to
 be logged, so they will be logged now.
You will find, if you try to open the files in the Domino Admin client that they are either corrupted or waiting to be configured or just not available and truncated.

So what to do? I tried fixup and that worked for the .nsf files. Trying to run it against the EsmMapDirTemplate.ntf file failed. I checked the downloaded update and sure enough when I went to look at the .JAR file it was inside, the .jar file threw an error at me and said it was malformed or corrupted.

Back to traveler 9.0, reinstall and all is good again. Now back to download a new 9.0IF1 and see if we can get this upgraded again

And for the record updating my Android client from the Appstore, which is now not in synch with the server client version. Either the way of the future, client side or going to be a problem in locked down companies perhaps?

Info below from http://ibm.com/support/fixcentral


Thursday, December 10, 2009

Q-SnTT - Quickr Qpconfig.xml Errors

Bart agrees about the qpconfig.xml

All together now, repeat after me, I will NOT edit the qpconfig.xml while sleep deprived or during the night while attending Lotusphere. I will not...

If you like the above graphic, go make one here.

Here is why:
12/09/2009 07:25:48 PM JVM: Java Virtual Machine initialized.
12/09/2009 07:25:49 PM Agent error: [Fatal Error] :69:5: The element type "user" must be terminated by the matching end-tag "</user>".
12/09/2009 07:25:52 PM org.xml.sax.SAXParseException: The element type "user" must be terminated by the matching end-tag "</user>".


What is this error in my server console telling me?

I have an agent run amok? A java agent at that.

And some org.xml.sax whatever? Come on guys, I'm an admin not a miracle java debugger.

But that /user thing rings a bell....

So here is what happened. It seems in my over zealous creative way, I had edited the qpconfig.xml and misplaced a reference. Who knew HTML was so unforgiving, or in this case XML. Raise your hands, me too, yes I know, my bad.

But in any event, here is what it looked like:
qpconfig bad

and what it should look like:
qpconfig good

Mote the juxtaposition of the /user field.

So if you get odd java/xml errors in your server console after editing your Qpconfig.xml file, guess you know where to start now don't you.

Thursday, June 25, 2009

MEMO - Mysterious Error Messages Obviously

I hope NOT to install this problem!
sametime is null error

Maybe this will be a new line of posts, MEMO's.

EDITED 1/2 hour later: Found reference in forums to an error after some further searching.

Explanation is:
Try removing C:\Program Files\Common Files\Installshield\Universal\Lotus* folders.
It will help in case this error is the result of the messed up installation.

Found we had 3 previous versions, including 802 listed, deleted them all and install went through fine.

Thursday, March 12, 2009

Lotus Notes Traveler 8.5 Update or How Not To Do It

We were updating our internal Lotus Domino 8.5 server with the latest Lotus Notes Traveler update from Fix Central ver8.5.0.1 (www.ibm.com/support/fixcentral).
One of my coworkers who hadn't done any work on Traveler yet was doing it and asked me how to install the update.
I hadn't thought about it and instead of saying, read the readme file, said run the exe.
I meant the download .exe so it would unzip.
Unfortunately for us the .exe file was run, but it was the ntraveler.exe. OOPS.

What to know what happens? Try it, in development, NOT production.
You get a lovely error in your Domino Server console which points to wherever you unzipped the file and ran the exe file. The usual process.exe has terminated abnormally.

Suffice it to say we did many things and finally the only way to resolve it we restarted the physical machine to clear any problems in memory and then reinstalled Traveler 8.5 and then properly installed the update.

It all works now.

So EDITED 3/12/2009: READ THE MANUAL and if you don't see it, search the IBM Toolbar or PlanetLotus.org or Google for it.

Friday, February 27, 2009

Calendar Profile...Don't you hate that error?

Keith Taylor commented about it from my last post, Fud Buster Friday #29, and I realized I never blogged it before although I see it EVERYWHERE.

There are numerous errors and issues, some are more obvious than others. These appear when you first start up Domino and the server is checking various points of interest, well points of it's own interest. You can also find these, if you never noticed them, in your statrep.nsf(using the infamous name, Monitoring Results) file. Select Events, By Severity.
This will also show you what is wrong in your server(s). Before you do this, be warned, not everything you see is bad, so pay attention and react accordingly. If you need help, ask me.

I will try to hit the main ones in this post.

1)Keep in mind, the most common reason, if you as the Admin open up an employee's mail file and look at the preferences under the more option in the mail file you will see YOUR name NOT the employee. You can either have the employee login and fix this by selecting their name or you will have to run a lotus script agent to resolve it. See more details here(technote #1088892). This is usually the way to do it but I will list a few more possibilities in case you see other messages.

2) SchedMgr: Error processing calendar profile document
(NoteID: NT0000XXXX) in database mail\UserMailFile.NSF: Can't find user in Name and Address Book

Basically what it says is the mail file exists but the user no longer does.
Move the mail file out of the Domino directory to your file server and this goes away. For more details(it's an adminp issue based on what YOU the admin tell it) see the technote #1089324.

3)"SchedMgr: Error processing calendar profile document (NoteID: NT0000xxxx) in database filename.nsf: Can't find $BusyName field on profile"

Also somewhat cryptic but obvious. If you can't find a name on the preferences field of course this won't work. Right? Right.

So you have a few ways to resolve this, read the technote it goes into detail and includes code for you to fix this.

I would have included more except IBM's support search site went down and I need to head out. May update this or post a 2nd entry on this topic if anyone has more odd profile issues they want answered.

Fud Buster Friday #29 - One Outage isn't so bad.. is it?

Naturally it depends on who has the outage and how long it lasts and well, a million other things.

As we know Google had an outage this week. Ho hum. Welcome to IT guys. The world keeps spinning, we get blamed, we fix it, life moves on. Or does it?

Just spent over a week on a server crashing daily problem, because of my laziness and lack of attention to the clients plight. Well, to be fair, I was at 2 new clients this week, plus demoing for a 3rd and rewiring my office but the bottom line is I took a casual liberty attitude with a clients business and that's not good.

The client is extremely happy I have resolved the problem, will wait 72 hours before total acceptance.

But this taught me, and should teach you too, that one outage is too many for ANY client. And repeated ones spell disaster for any IT credit or expectations and it is VERY hard to recover from this and in some cases leads the customer to think about alternative email solutions.

The client had turned down clustering, even a backup replicated server(I am sure some PC could have been found but I digress). Their backup procedures are appalling and they have no idea why they were running LDAP, POP3,DECS, DIIOP or IMAP on the server. (Note to jr admins, just because you see a check box does NOT mean it must be checked.)

The server was throwing out the usual errors about calendar profiles, users not found in the NAB and a bunch of agent signing errors, which happen to run their apps but signed by a previous admin/developer, of course. And they had small quotas like 150MB. And of course you can guess which mail files had these errors. Funny how nonexistent people can fill up a mail file,waste disk space, routing, backup time and space and even have agents running! Also, if you have a donotreply@corp.com address, be prepared to have many replies to it. The fix is to just have an entry in the NAB and a mail file for it that purges every day or 7 or whatever you want. Otherwise, like the client, you could have 100's of dead mails in your 4 mail.box files.

Suggested to the client to take care of these, only to realize they could have been all along and never did. So as any good consultant would, we billed them for the mini clean up and are planning on a bigger clean up under a new project.

I saw the errors upfront, but we were working on a (thought we were)bigger problem and could fix these later. Remember, Eat the Frog, do the stuff you don't like or want to first and move forward. Taking the easy way out will never help you as an admin.

The other thing is delegate. It was bumped to me as others had tried to tackle it already. I was not happy none of them had resolved the errors or the small things.

Training is important, but walk the talk. As the Worst Practices session at LS08 showed, even the great ones don't always follow their own guidelines.

So I apologized to the client and oddly enough they were just happy anyone could resolve the problem. It has been a month or so off and on.

The downside is their clients just expect the server to be down and even if it stays up won't care. The worst part, for me, was after it all, they tell me they are going to move off Domino for mail. Working on that problem next and may blog it if it gets interesting.

Thursday, February 19, 2009

SnTT - NIF means NOT INDEXING FULLY

Sometimes I need to be more granular than I am when troubleshooting problems.
I don't like to be because I feel it inhibits my ability to grok the total issue.
But some servers just demand it.

Admittedly NIF stands for Notes Indexing Facility. But my explanation is more accurate when it is not functioning.

So I ran DCT, the excellent Domino Configuration Tuner on the clients Domino Windows server running 703FP1, after temporarily installing the 8.5 client on the server.

It of course told me the basics I know already, mutlithread the full text index, enhance various other notes.ini settings like:
UPDATE_FULLTEXT_THREAD=1
SERVER_NAME_LOOKUP_NO_UPDATE=1
DEBUG_ENABLE_UPDATE_FIX=8191
NSF_BACKUP_MEMORY_CONSTRAINED=1
SF_BACKUP_MEMORY_LIMIT=104857600

and my personal favorite: view_rebuild_dir=e:\lotustemp\

This last line allows you to specify where the temporary space required for the rebuilds are located. always helpful when one of the hard drives is running low and can lead to other issues.

The bottom line is the problem occurs and it seems to be an agent which is stuck. Thought about and DCT confirmed, web agents were not running concurrently, trying that change too.

Enable agents to run asynchronously through the Server document -> Internet Protocols -> Domino Web Engine tab. Under Web Agents, enable the "Run Web Agents Concurrently" setting.

And found a very corrupted file, which turned out to be some bad restored file anyway.
Cleared it all and what happened? dead server in 2 days instead of 1. Improvement yes, fixed, no.

Called IBM Support, I had done more than my usual efforts and was tired of trying.

They suggested using the line, ftg_use_sys_memory=1, which came out in 5.0.9, link to the technote.
This will instruct the full-text (FT) engine to use direct malloc calls from the operating system for large allocations, instead of requesting memory through the Notes Memory Manager.


And we wait to see if this indeed fixed it as IBM suggested. Updated late Wen. night, it did not resolve it, although it hung on longer.

Issue seems to be when users are logging in during the morning, I wonder about peaking or utilization.

Thursday, November 20, 2008

QSnTT - When an Error Message Gets Misplaced

My Browser is a Notes Client?! Call the UX lab
Quickr Show n Tell is Back Again



Sometimes one gets away from you. This must be Quickr's for R8.1.
I received this after converting a Quickr server from using LDAP as it's Directory to Domino as it's Directory.

I am using a browser, yet the error believes me to be using a Notes Client. Has Lotus taken over Firefox? Has Firefox embedded a Notes Client in itself?

Remember to revert any changes in the qpconfig.xml for LDAP when doing this.

Evidently there are some hard coded references to LDAP or Domino Directory in the Main.nsf that must get touched (or reinstalled). Anyone who's done this let me know, Stuart and I have similar issue doing the exact reverse processes. He is going to LDAP from Domino Directory.

UPDATED 30 minutes later: My problem was a looping caused by 2 references in the DA file and removing the 2nd NAB from the Quickr server. So we are back on LDAP, now to fix port 636 to be open at the firewall for SSL LDAP. Never a dull minute.

Thursday, June 26, 2008

Microsoft.com is down, so much for Hyper-V


Can't help myself with this one.
Click on it to see it larger.

I am sure IBM Global services could help them, but something tells me they will not ask for help.