Notes 会话与 Lotus 会话 COM API 问题
我维护一个相当大的应用程序，它与 Lotus Notes 进行大量通信。最近在过去的几个月中，一些用户在连接到 Lotus Notes 会话时遇到问题，我使用以下代码来获取会话
Set Session = CreateObject("Notes.NotesSession")
此错误似乎仅针对特定数量的用户弹出。我使用以下行创建了一个示例应用程序
Set Session = CreateObject("Lotus.NotesSession")
，并且上面的行由于某种原因起作用。用户表示安装笔记时出现一些问题，但重新安装后已得到纠正。为什么同一个对象有两个类名，为什么一个类名起作用而另一个类名不起作用。
关于如何解决这些 API 问题有什么想法吗？
I maintain a fairly large application which does a lot of talking with Lotus Notes. Recently in the last couple of months, some users have been having problem connecting to the Lotus Notes Session, I use the following code to get the session
Set Session = CreateObject("Notes.NotesSession")
This error seems to be popping up only for a certain number of users. I created a sample app with the following line
Set Session = CreateObject("Lotus.NotesSession")
And the above line works for some reason. The user says there was some issue installing notes but has been rectified after a re-installation. Why are there two class names for the same object and why is one working an other one not working.
Any ideas on how to resolve these API issues?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
这个 documentation 提到
Notes.NotesSession是基于 OLE 的，我不知道为什么 OLE 类在 COM 类没有的情况下失败，但考虑到 OLE 现在已经有二十年的历史了，我会坚持使用
Lotus.NotesSessionThis documentation on IBM's site mentions that
Notes.NotesSessionis OLE based,I don't know specifically why the OLE classes are failing where the COM classes do not, but given that OLE is two decades old now, I would stick with
Lotus.NotesSession没什么可继续的，但我会抛出 ProcMon 并查看注册表项和当您请求此对象时，文件正在被命中。
Not much to go on, but I'd throw ProcMon at it and see what registry keys and files are being hit when you request this object.
对于所使用的登录名，Notes 名称和密码仍必须是“当前”。如果帐户已过期或需要重新认证，访问可能会被阻止？
The Notes-Name and password still have to be 'current' for the login used. If the account has expired or requires recertification, access may be blocked?