The call to NotesInitExtended failed: 417 (notes_sess_open|1235|7890|0)

Hi, I am getting this message from my Networker Backup software when trying to run my Notes backup: "The call to NotesInitExtended failed: 417 (notes_sess_open|1235|7890|0)". I need help in determining what is the cause of this and how I can clear it. I can't seem to get a backup with this problem.

Thanks, Juan
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sjef BosmanGroupware ConsultantCommented:
Could it be that the backup software isn't compatible (any more) with your Domino version? Did you recently install newer versions of either Domino and/or your Backup software?
Sjef BosmanGroupware ConsultantCommented:
By the way, which versions do you have/use, of Domino and Backup? And what environment do you have, which Windows server (or Linux)?
wishdAuthor Commented:
Hi, we have not changed the version of any of our software for Networker or Domino 8.5.2. We are running it on a Windows Server 2003 R2 SP2. The only thing we were doing before this occurred was trying the "Move..." option on an individual mail database. This is what I did:

1) Right clicked on the Database under Files Tab.
2) Selected "Move..."
3) On the left side pane on the bottom selected "Other..."
4) Dialog box comes up and typed the path for the new storage place.
5) Then click the OK button.

Other than that we haven't changed anything in regards to software. I am wondering if there is a process hung up maybe that was caused by the "Move..." from above and that is why we are getting the error.??
Starting with Angular 5

Learn the essential features and functions of the popular JavaScript framework for building mobile, desktop and web applications.

Sjef BosmanGroupware ConsultantCommented:
I can't imaging it's the Move. I read somewhere that a restart of the server solved a similar problem. Did you already try that?
wishdAuthor Commented:
I did not try a restart, yet, because it is during regular work hours right now. Since you brought that up though I was wondering if  I am to reboot the server what the proper way to bring it down is? FYI: I have been learning Notes/Domino on the job. No formal training. The last time it needed to be rebooted it ran through a consistency check that took a while, maybe an hour, before mail was up and running again. Is there a way for it not to run through that check or is it recommended or just part of the boot up process?
Sjef BosmanGroupware ConsultantCommented:
Usually, when properly installed, Domino shuts down when you shut down the server or the service. How is Domino started on the server? If it's a service, you should go to the Services list in the Administration Console somewhere, stop the service, wait until it's stopped and then restart it.
wishdAuthor Commented:
So I do not have to physically reboot the host computer? Just stop the service and then when it is stopped restart it? It is a service under the services and is set to manual. When we have rebooted in the past I have just stopped the service and then physically rebooted the server and when the server came back up I would start the Lotus Server Service and it has always started with the consistency check first that takes a good hour. I would like to avoid that long hour if possible.
Sjef BosmanGroupware ConsultantCommented:
Oh, goodness... Ok, you can also stop the server using the Server Console in the Admin client: just type quit and it stops. Then restart the service.
my answer to your other issue applies here too.  It is NOT normal to start Domino and experience delays due to consistency checking.  This is the same as driving on with an engine warning light on in your car.  Continuing to do this is choosing to live life dangerously and taking unwaranted risks with your data.

The correct way would be to issue a quit command on the Domino console, and wait for the server to display the text "Server shutdown complete".  Then proceed to shutdown the server.

Also, Domino works a lot better if you enable Transaction logging. See the Domino Wiki. Another great resource is the IBM Lotus Notes and Domino 8 Deployment Guide

While your at it, read about DAOS.  And if your backup product really supports Domino, it will benefit from transaction logging too, in that the server need not be taken down.
Sjef BosmanGroupware ConsultantCommented:
@Lars: IMHO a Windows-based Domino server should be shut down correctly and automatically when the Windows server is shut down. So this should not be the reason why a consistency check is needed every time the server is started. Which leads to the questions: how exactly is Domino installed, and how is the system shut down?

> Domino works a lot better if you enable Transaction logging
If you define "better" as: faster, longer, productive, then I tend to disagree with your statement. Transaction logging takes both time and space. On the other hand, if "better" is "more reliable in case of database problems caused by external factors", I could agree with you. Someone whose server is running reliably, no issues whatsoever, for 60 days or more, why should he enable Transaction logging? By the way, up-times like that are quite common on Linux-based installations...
wishdAuthor Commented:
I restarted the server and I am still seeing the same error.
Sjef BosmanGroupware ConsultantCommented:
Still, this page gives me the impression that something must have changed in your environment.

The only suggestions left are:
- contact the creators of the backup product
- change to a different backup product

Sjef, I am disappointed that you go against established best practices in Domino Administration.  See Notes/Domino Best Practices: Master Checklist
From this article:
Below is a list of articles that every Notes/Domino application designer, administrator, and IT manager should read, regardless of their responsibilities.
Transaction logging is required for DAOS. See DAOS Best Practices and DAOS Deployment Guide.
lt also enables other backup options, see Notes/Domino Best Practices: Transaction Logging

Note that the supplied links also contain a lot of links with supporting material. Before executing a set of changes, please make a plan, and read through the supplied documentation if any conflicts exist.  Make sure your plan is complete, and contains the reasons for adhering to or deviating from Best Practices.  If possible, get a Domino expert to read through the plan for any unfortunate mistakes.  Get the plan approved and execute it.

Then, marvel at how much fun it is to use a well configured and maintained Domino system.
Sjef BosmanGroupware ConsultantCommented:
These are disappointing times...

I'd love to see some test results of the performance of a Domino server with and without transaction logging. I tried to find some benchmarks but couldn't find any.

By the way: any comments on wishd's original question?
wishdAuthor Commented:
I checked with EMC (Netwoker) and they stated the this is a notes issue and not a networker issue.  According to them NotesInitExtended is a Lotus notes API function. I still do not have a resolution.
Sjef BosmanGroupware ConsultantCommented:
Firstly, they are right of course: NotesInitExtended is indeed a Notes API function. But it's their software that uses it, so IMHO, their attitude could (and should) have been a lot more helpful.  The message 'The call to NotesInitExtended failed: 417 (notes_sess_open|1235|7890|0)' is from their software, so it should tell them a lot. What exactly does that message mean, can they tell you that at least? Instead of letting you struggle with an incomprehensible error message?

I checked some of their error pages with references to NotesInitExtended, and they more or less suggest a configuration problem, e.g. an incorrectly configured user. I assume you verified it all at least three times by now??
wishdAuthor Commented:
Hi Sjef Bosman,

The email server has not stopped working (luckly) we have not made any configuration changes in the last 6 years and backups were running with no problems until last Monday when we started to get the errors.
Sjef BosmanGroupware ConsultantCommented:
Still, Notes documents and files can get corrupted...
wishdAuthor Commented:
this issue was resolved by stopping the Notes service. Setting it to manual then rebooting the server. I started the service manually and it worked.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sjef BosmanGroupware ConsultantCommented:
So you say that Networker Backup doesn't work on a Domino server that's set to run Domino as a service? That seems mighty strange to me. Did you contact your supplier about this?

Another inconsistency: you stated before that "It is a service under the services and is set to manual" whereas your "solution" above says that you had to set it to manual. What happened?? Please explain.
wishdAuthor Commented:
@sjef Bosman, read my solution a little bit more carefully. I stated that the system worked after I set the service to run manually. Once I restarted the service (manually) it worked.
Sjef BosmanGroupware ConsultantCommented:
Thanks, but I think I didn't need the advice. Sure, it may be my limited knowledge of the English language, or my lack of detailed knowledge of the Windows services, but I absolutely fail to see what I should be seeing according to you.  :-O

I'll ask a native speaker to look into this.
wishdAuthor Commented:
I apologize if I offended you with my response. I just wanted to clarify my answer to this issue in case it could help a fellow it admin with a similar issue.
Steve KnightIT ConsultancyCommented:
Not sure how this would help unless your backup solution service start times is clashing with Domino.  Is it alright if you set Domino back to "Automatic" start now?  

Domino will always happily start and shut down with Windows, only real exception is if it takes too long to shutdown then Windows won't wait for ever.  In that case it could be closed off un cleanly and cause a need for consistency checks after start.

Default is 20 or 30 seconds I think, a google should find you the relevant registry key, think it was WaitKillService or something.

So if it does do it again it needs seeing why, but firstly see how long it takes to go from a quit command or Stop signal to the service to the last n*.exe being loaded.
Steve KnightIT ConsultancyCommented:
I'm still confused frankly when you said in http#a39766070 that the service is set to Manual already and so then saying to start it manually and it worked seems pretty odd?

Do you mean instead of having it set as a service you know have it started as a program?

You already said the service was set to manual so after a server reboot it would obviously sit there waiting service to be started and if it shut down cleanly it should start cleanly.  Even if it didn't shut down cleanly and you had transaction logging turned on -- circular logging of 4Gb say would be fine, ideally to a different disc -- then you can bring it up and it replays any logs and boots quickly if there is a fault.

So mainly revolves around how it shuts down I would say?
wishdAuthor Commented:
I was up and running immediately after restarting the service.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Lotus IBM

From novice to tech pro — start learning today.