Creating a new Teams meeting does not work #103

jarkkopie · 2021-08-10T10:44:22Z

jarkkopie
Aug 10, 2021

I'm testing this feature, but can't make it to work with my M365 environment. Token is successfully retrieved and validated, but when I try to schedule meeting to Teams, I got error "The HTTP Request operation failed,". With debugging enabled I found this error from my log:

2021.08.10 13.26.03 Error #1401: The HTTP Request operation has failed.
Library: domiIntegrator.Class: DominoOnlineMeetingIntegrator.DOMEETINGREQUESTRAW(); line #899
HTTP/1.1 400 Bad Request

Stack Logging is Disabled

Meeting Service: teams
TOKEN TYPE: Bearer
Meeting URL: https://graph.microsoft.com/v1.0/me/onlineMeetings
responsecode: HTTP/1.1 400 Bad Request
responsejson: {"error":{"code":"General","message":"Request payload cannot be null.","innerError":{"request-id":"xxx","date":"2021-08-10T10:26:02","client-request-id":"xxx"}},"responsecode":"HTTP/1.1 400 Bad Request"}

Body JSON
{"subject":"toinen","startDateTime":"2021-08-11T10.00.00+02:00","endDateTime":"2021-08-11T13.00.00+02:00"}

2021.08.10 13.26.03 Library: domiUtilsFE.DOMINOTIFYRESULT():
DOMI Failure
domi.ErrorCode: 1401
domi.ErrorMessage: The HTTP Request operation has failed.
domi.ResponseCode: HTTP/1.1 400 Bad Request
domi.HTTPstatusCodeType: 4xx Client Error: The request contains bad syntax or cannot be fulfilled

What might be wrong with my installation? The current Notes version is 11.0.1FP3
-Jarkko

paulswithers · 2021-08-10T14:42:08Z

paulswithers
Aug 10, 2021
Maintainer

Please check the URL in DOMIConstantsBE Script Library, making sure it looks like https://github.com/HCL-TECH-SOFTWARE/domino-online-meeting-integration/blob/main/notes/Code/ScriptLibraries/domiConstantsBE.lss#L45. A fix was applied a couple of months ago to remove the trailing "/" from the URL. It sounds like you're still on an older version, which will be impacted by a fix on the web server done recently.

We recommend updating to the latest code.

2 replies

jarkkopie Aug 11, 2021
Author

Thanks Paul, but this version is not the case. I updated it again and URL seems to be ok. Still got the errors. -Jarkko

Domino Online Meeting Integration, 20 JUL 2021, Version: 1.0.3 HF1, Build: 1.12D3
2021.08.11 15.37.01 Library: NotesRESTconsumer.Class: NotesRESTconsumer.PROCESSREQUEST():
Response Code: HTTP/1.1 400 Bad Request
2021.08.11 15.37.01 Library: NotesRESTconsumer.Class: NotesRESTconsumer.PROCESSREQUEST(): Http POST: HTTP/1.1 400 Bad Request

POST Headers JSON
{
"Content-Type":"application/json",
"Authorization":"**********"
}

POST Body JSON
{
"subject":"sdfa",
"startDateTime":"2021-08-12T08.00.00+02:00",
"endDateTime":"2021-08-12T08.30.00+02:00"
}

2021.08.11 15.37.02 Error #1401: The HTTP Request operation has failed.
Library: domiIntegrator.Class: DominoOnlineMeetingIntegrator.DOMEETINGREQUESTRAW(); line #899
HTTP/1.1 400 Bad Request

Stack Logging is Disabled

Meeting Service: teams
TOKEN TYPE: Bearer
Meeting URL: https://graph.microsoft.com/v1.0/me/onlineMeetings
responsecode: HTTP/1.1 400 Bad Request
responsejson: {"error":{"code":"General","message":"Request payload cannot be null.","innerError":{"request-id":"xxx","date":"2021-08-11T12:37:01","client-request-id":"xxx"}},"responsecode":"HTTP/1.1 400 Bad Request"}

Body JSON
{"subject":"sdfa","startDateTime":"2021-08-12T08.00.00+02:00","endDateTime":"2021-08-12T08.30.00+02:00"}

2021.08.11 15.37.02 Library: domiUtilsFE.DOMINOTIFYRESULT():
DOMI Failure
domi.ErrorCode: 1401
domi.ErrorMessage: The HTTP Request operation has failed.
domi.ResponseCode: HTTP/1.1 400 Bad Request
domi.HTTPstatusCodeType: 4xx Client Error: The request contains bad syntax or cannot be fulfilled

2021.08.11 15.37.04 LotusScript Finished

jarkkopie Sep 10, 2021
Author

Hi @paulswithers ,

I updated the code to 1.0.5 Build 1.1588 and still facing the same issue. domiConstantsBE is also checked:

According to the log, the problem is still that M365 is reporting about an bad request:

===
2021.09.10 10.35.29 Error #1401: The HTTP Request operation has failed.
Library: domiIntegrator.Class: DominoOnlineMeetingIntegrator.DOMEETINGREQUESTRAW(); line #899
HTTP/1.1 400 Bad Request

Stack Logging is Disabled

Meeting Service: teams
TOKEN TYPE: Bearer
Meeting URL: https://graph.microsoft.com/v1.0/me/onlineMeetings
responsecode: HTTP/1.1 400 Bad Request
responsejson: {"error":{"code":"General","message":"Request payload cannot be null.","innerError":{"request-id":"56aab306-7c54-4bf0-87ba-fdfa57d2b628","date":"2021-09-10T07:35:29","client-request-id":"56aab306-7c54-4bf0-87ba-fdfa57d2b628"}},"responsecode":"HTTP/1.1 400 Bad Request"}

So, something is broken in my installation?

-Jarkko

jarkkopie · 2021-12-29T06:49:24Z

jarkkopie
Dec 29, 2021
Author

@paulswithers

After much research, I discovered that the Windows regional format affects the operation of the DOMI. Creating a new appointment works if I change the Windows format to English (US). With Finnish format I always get an error message "Bad request".

Oddly enough, console.log looks exactly the same, so the JSON message has the same date and time format regardless of the Windows settings. So is this a bug or is DOMI also supported in other language formats than US?

The tests are done with the template that comes with Notes 12.0.1. The logs are below for the successful and unsuccessful creation of the appointment.

-Jarkko

Successful log / Regional format: English (United States):
[4310:0002-1BBC] LSXBE HTTP debug information type: HTTP Request header:
[4310:0002-1BBC] POST /v1.0/me/onlineMeetings HTTP/1.1
[4310:0002-1BBC] Host: graph.microsoft.com
[4310:0002-1BBC] User-Agent: libcurl-agent/1.0
[4310:0002-1BBC] Accept: /
[4310:0002-1BBC] Content-Type: application/json
[4310:0002-1BBC] Authorization: Bearer eyJ0eXAiOiJKV1QiLCJub25jZSI6ImN5aU8xY1FiNDdYT3U5Y0RPemZ2bmpqLXluNmdJV1ZTdlVHYjRFM2g4LVEiLCJ
[4310:0002-1BBC] LSXBE HTTP debug information type: HTTP Request SSL data:
[4310:0002-1BBC]
[4310:0002-1BBC] LSXBE HTTP debug information type: HTTP Request data:
[4310:0002-1BBC] {"subject":"Meeting","startDateTime":"2021-12-29T12:00:00+02:00","endDateTime":"2021-12-29T12:30:00+02:00"}
[4310:0002-1BBC] LSXBE HTTP debug information type: Generic Information:
[4310:0002-1BBC] We are completely uploaded and fine
[4310:0002-1BBC] LSXBE HTTP debug information type: HTTP Response SSL data:
[4310:0002-1BBC]
[4310:0002-1BBC] LSXBE HTTP debug information type: Generic Information:
[4310:0002-1BBC] Mark bundle as not supporting multiuse
[4310:0002-1BBC] LSXBE HTTP debug information type: HTTP Response header:
[4310:0002-1BBC] HTTP/1.1 201 Created
[4310:0002-1BBC] LSXBE HTTP debug information type: HTTP Response header:
[4310:0002-1BBC] Date: Wed, 29 Dec 2021 06:20:34 GMT

Failed log / Regional format: Finnish (Finland):
[1CD0:0002-4160] LSXBE HTTP debug information type: HTTP Request header:
[1CD0:0002-4160] POST /v1.0/me/onlineMeetings HTTP/1.1
[1CD0:0002-4160] Host: graph.microsoft.com
[1CD0:0002-4160] User-Agent: libcurl-agent/1.0
[1CD0:0002-4160] Accept: /
[1CD0:0002-4160] Content-Type: application/json
[1CD0:0002-4160] Authorization: Bearer eyJ0eXAiOiJKV1QiLCJub25jZSI6ImN5aU8xY1FiNDdYT3U5Y0RPemZ2bmpqLXluNmdJV1ZTdlVHYjRFM2g4LVEiLCJ
[1CD0:0002-4160] LSXBE HTTP debug information type: HTTP Request SSL data:
[1CD0:0002-4160]
[1CD0:0002-4160] LSXBE HTTP debug information type: HTTP Request data:
[1CD0:0002-4160] {"subject":"Meeting","startDateTime":"2021-12-29T13.00.00+02:00","endDateTime":"2021-12-29T13.30.00+02:00"}
[1CD0:0002-4160] LSXBE HTTP debug information type: Generic Information:
[1CD0:0002-4160] We are completely uploaded and fine
[1CD0:0002-4160] LSXBE HTTP debug information type: HTTP Response SSL data:
[1CD0:0002-4160] Ω
[1CD0:0002-4160] LSXBE HTTP debug information type: Generic Information:
[1CD0:0002-4160] Mark bundle as not supporting multiuse
[1CD0:0002-4160] LSXBE HTTP debug information type: HTTP Response header:
[1CD0:0002-4160] HTTP/1.1 400 Bad Request
[1CD0:0002-4160] LSXBE HTTP debug information type: HTTP Response header:
[1CD0:0002-4160] Date: Wed, 29 Dec 2021 06:22:50 GMT

0 replies

jarkkopie · 2021-12-30T12:59:40Z

jarkkopie
Dec 30, 2021
Author

I still tried different some language settings in Windows 10. In addition to the regional setting English (United States), DOMI also works with the German language setting, despite the fact that the date and time formats are exactly the same as in Finland.

So the conclusion is finally that DOMI DOES NOT work in Windows with the Regional setting set to Finnish (Finland) or English (Finland).

This DOMI is one of the most important features to upgrade Notes and Domino to V12.0.1. Finnish client 12.0.1 is also coming, so I guess this feature is really needed.

1 reply

ajithtpillai Oct 1, 2024

reported in #146
this is fixed in 14.0 via SPR PDARCXBJUW: Unable to create DOMI online meeting for Finnish language

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Creating a new Teams meeting does not work #103

{{title}}

Replies: 3 comments 3 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Creating a new Teams meeting does not work #103

jarkkopie Aug 10, 2021

Replies: 3 comments · 3 replies

paulswithers Aug 10, 2021 Maintainer

jarkkopie Aug 11, 2021 Author

jarkkopie Sep 10, 2021 Author

jarkkopie Dec 29, 2021 Author

jarkkopie Dec 30, 2021 Author

ajithtpillai Oct 1, 2024

jarkkopie
Aug 10, 2021

Replies: 3 comments 3 replies

paulswithers
Aug 10, 2021
Maintainer

jarkkopie Aug 11, 2021
Author

jarkkopie Sep 10, 2021
Author

jarkkopie
Dec 29, 2021
Author

jarkkopie
Dec 30, 2021
Author