Hi all,

We have implemented 11.1.4 and suddenly there is a problem with Excel-attachments when e-mails are sent to receivers using Outlook365. When the mail arrives it has an attachment named like "=utf-8BU8OkbGpzdMOkbGxlcmFwcG9ydF9zdi1zZV9J= =utf-8BTkxBTkRTQkFOQU5fb2t0LTIwMTkueGxzeA===" which can't be opened.

When sending the same mail to any other type of mail-system the Excel-file is correctly attached.

What's even more puzzling is that it doesn't happen for all reports, only for some. I found an old page from IBM suggesting to set RSVP.EXCEL.EXCEL_2007_FILE_ZIP to true. This doesn't seem to have any effect anymore judging from looking at the attachment in hex-format.

Has anyone of you seen this and hopefully found a solution?

Best regards


------------------------------
Håkan Alvgren
------------------------------

#CognosAnalyticswithWatson

Hi Håkan, 

Do you have Scandinavian characters in the report name? One my clients claimed that this was happening on their reports until the Scandinavian characters were removed from the report name. If this is the case and workaround works, I would recommend raising this as support case as it is most likely a bug. 

I hope this helps.

------------------------------
JANNE LIND
------------------------------

Original Message:
Sent: Tue November 05, 2019 02:22 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Hi all,

We have implemented 11.1.4 and suddenly there is a problem with Excel-attachments when e-mails are sent to receivers using Outlook365. When the mail arrives it has an attachment named like "=utf-8BU8OkbGpzdMOkbGxlcmFwcG9ydF9zdi1zZV9J= =utf-8BTkxBTkRTQkFOQU5fb2t0LTIwMTkueGxzeA===" which can't be opened.

When sending the same mail to any other type of mail-system the Excel-file is correctly attached.

What's even more puzzling is that it doesn't happen for all reports, only for some. I found an old page from IBM suggesting to set RSVP.EXCEL.EXCEL_2007_FILE_ZIP to true. This doesn't seem to have any effect anymore judging from looking at the attachment in hex-format.

Has anyone of you seen this and hopefully found a solution?

Best regards


------------------------------
Håkan Alvgren
------------------------------

#CognosAnalyticswithWatson

Hi Janne,

You're absolutely correct. I found a couple of problems and I will try to report them:

1) In EventStudio you can't have national characters in the report name or in the burst label if the package comes from Framework Manager. It's strange but it seems to work if the package is a dynamic cube.

2)There seems to be a migration problem for some jobs and then national characters in the report name didn't work. These jobs were identified by having no activities when opened but the showed activities when opened in "Classic view". I had to redo those jobs from scratch and then everything seems to work as expected.

What I still can't understand is why this problem seems to be limited to recipients using Outlook365.

------------------------------
Håkan Alvgren
------------------------------

Original Message:
Sent: Tue November 05, 2019 06:07 AM
From: JANNE LIND
Subject: Problem with Outlook365 and attached Excel-files

Hi Håkan, 

Do you have Scandinavian characters in the report name? One my clients claimed that this was happening on their reports until the Scandinavian characters were removed from the report name. If this is the case and workaround works, I would recommend raising this as support case as it is most likely a bug. 

I hope this helps.

------------------------------
JANNE LIND

Original Message:
Sent: Tue November 05, 2019 02:22 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Hi all,

We have implemented 11.1.4 and suddenly there is a problem with Excel-attachments when e-mails are sent to receivers using Outlook365. When the mail arrives it has an attachment named like "=utf-8BU8OkbGpzdMOkbGxlcmFwcG9ydF9zdi1zZV9J= =utf-8BTkxBTkRTQkFOQU5fb2t0LTIwMTkueGxzeA===" which can't be opened.

When sending the same mail to any other type of mail-system the Excel-file is correctly attached.

What's even more puzzling is that it doesn't happen for all reports, only for some. I found an old page from IBM suggesting to set RSVP.EXCEL.EXCEL_2007_FILE_ZIP to true. This doesn't seem to have any effect anymore judging from looking at the attachment in hex-format.

Has anyone of you seen this and hopefully found a solution?

Best regards


------------------------------
Håkan Alvgren
------------------------------

#CognosAnalyticswithWatson

Hi Håkan,

We see the same problems with Outlook365 as the recipients mail program, what we found is if the report name is shorter than 32 characters it seems to go fine with Scandinavian characters.

Br
René

------------------------------
René Kent Nielsen
Solutions Architect
CogniTech A/S
Herning
------------------------------

Original Message:
Sent: Wed November 06, 2019 03:27 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Hi Janne,

You're absolutely correct. I found a couple of problems and I will try to report them:

1) In EventStudio you can't have national characters in the report name or in the burst label if the package comes from Framework Manager. It's strange but it seems to work if the package is a dynamic cube.

2)There seems to be a migration problem for some jobs and then national characters in the report name didn't work. These jobs were identified by having no activities when opened but the showed activities when opened in "Classic view". I had to redo those jobs from scratch and then everything seems to work as expected.

What I still can't understand is why this problem seems to be limited to recipients using Outlook365.

------------------------------
Håkan Alvgren

Original Message:
Sent: Tue November 05, 2019 06:07 AM
From: JANNE LIND
Subject: Problem with Outlook365 and attached Excel-files

Hi Håkan, 

Do you have Scandinavian characters in the report name? One my clients claimed that this was happening on their reports until the Scandinavian characters were removed from the report name. If this is the case and workaround works, I would recommend raising this as support case as it is most likely a bug. 

I hope this helps.

------------------------------
JANNE LIND

Original Message:
Sent: Tue November 05, 2019 02:22 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Hi all,

We have implemented 11.1.4 and suddenly there is a problem with Excel-attachments when e-mails are sent to receivers using Outlook365. When the mail arrives it has an attachment named like "=utf-8BU8OkbGpzdMOkbGxlcmFwcG9ydF9zdi1zZV9J= =utf-8BTkxBTkRTQkFOQU5fb2t0LTIwMTkueGxzeA===" which can't be opened.

When sending the same mail to any other type of mail-system the Excel-file is correctly attached.

What's even more puzzling is that it doesn't happen for all reports, only for some. I found an old page from IBM suggesting to set RSVP.EXCEL.EXCEL_2007_FILE_ZIP to true. This doesn't seem to have any effect anymore judging from looking at the attachment in hex-format.

Has anyone of you seen this and hopefully found a solution?

Best regards


------------------------------
Håkan Alvgren
------------------------------

#CognosAnalyticswithWatson

Thanks René,

Yes you are correct, when I look at the failing reports the file name is 32 characters or longer. I have opened a case with IBM and will add this info.

Regards,

------------------------------
Håkan Alvgren
------------------------------

Original Message:
Sent: Thu November 07, 2019 06:03 AM
From: René Kent Nielsen
Subject: Problem with Outlook365 and attached Excel-files

Hi Håkan,

We see the same problems with Outlook365 as the recipients mail program, what we found is if the report name is shorter than 32 characters it seems to go fine with Scandinavian characters.

Br
René

------------------------------
René Kent Nielsen
Solutions Architect
CogniTech A/S
Herning

Original Message:
Sent: Wed November 06, 2019 03:27 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Hi Janne,

You're absolutely correct. I found a couple of problems and I will try to report them:

1) In EventStudio you can't have national characters in the report name or in the burst label if the package comes from Framework Manager. It's strange but it seems to work if the package is a dynamic cube.

2)There seems to be a migration problem for some jobs and then national characters in the report name didn't work. These jobs were identified by having no activities when opened but the showed activities when opened in "Classic view". I had to redo those jobs from scratch and then everything seems to work as expected.

What I still can't understand is why this problem seems to be limited to recipients using Outlook365.

------------------------------
Håkan Alvgren

Original Message:
Sent: Tue November 05, 2019 06:07 AM
From: JANNE LIND
Subject: Problem with Outlook365 and attached Excel-files

Hi Håkan, 

Do you have Scandinavian characters in the report name? One my clients claimed that this was happening on their reports until the Scandinavian characters were removed from the report name. If this is the case and workaround works, I would recommend raising this as support case as it is most likely a bug. 

I hope this helps.

------------------------------
JANNE LIND

Original Message:
Sent: Tue November 05, 2019 02:22 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Hi all,

We have implemented 11.1.4 and suddenly there is a problem with Excel-attachments when e-mails are sent to receivers using Outlook365. When the mail arrives it has an attachment named like "=utf-8BU8OkbGpzdMOkbGxlcmFwcG9ydF9zdi1zZV9J= =utf-8BTkxBTkRTQkFOQU5fb2t0LTIwMTkueGxzeA===" which can't be opened.

When sending the same mail to any other type of mail-system the Excel-file is correctly attached.

What's even more puzzling is that it doesn't happen for all reports, only for some. I found an old page from IBM suggesting to set RSVP.EXCEL.EXCEL_2007_FILE_ZIP to true. This doesn't seem to have any effect anymore judging from looking at the attachment in hex-format.

Has anyone of you seen this and hopefully found a solution?

Best regards


------------------------------
Håkan Alvgren
------------------------------

#CognosAnalyticswithWatson

Hello all,

I am obviously fighting with the same problem. While testing I have noticed following with names of the reports/report views:

• Report name: "äöå äöå äöå äöå", 15 characters, OK
• Report name: "äöå äöå äöå äöå äöå", 19 characters, FAILED
• Report name: "Kehitysyhteistyömäärärahat", 25 characters, OK
• Report name: "Ministeriön Kehitysyhteistyömäärärahat", 38 characters, FAILED

(yeah, the first two report names are meaningless, even in Finnish ;). 

So report names shorter than 32 character might cause failing also. 

Cheers,

------------------------------
Mikko Pietilä
------------------------------

Original Message:
Sent: Thu November 07, 2019 07:05 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Thanks René,

Yes you are correct, when I look at the failing reports the file name is 32 characters or longer. I have opened a case with IBM and will add this info.

Regards,

------------------------------
Håkan Alvgren

Original Message:
Sent: Thu November 07, 2019 06:03 AM
From: René Kent Nielsen
Subject: Problem with Outlook365 and attached Excel-files

Hi Håkan,

We see the same problems with Outlook365 as the recipients mail program, what we found is if the report name is shorter than 32 characters it seems to go fine with Scandinavian characters.

Br
René

------------------------------
René Kent Nielsen
Solutions Architect
CogniTech A/S
Herning

Original Message:
Sent: Wed November 06, 2019 03:27 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Hi Janne,

You're absolutely correct. I found a couple of problems and I will try to report them:

1) In EventStudio you can't have national characters in the report name or in the burst label if the package comes from Framework Manager. It's strange but it seems to work if the package is a dynamic cube.

2)There seems to be a migration problem for some jobs and then national characters in the report name didn't work. These jobs were identified by having no activities when opened but the showed activities when opened in "Classic view". I had to redo those jobs from scratch and then everything seems to work as expected.

What I still can't understand is why this problem seems to be limited to recipients using Outlook365.

------------------------------
Håkan Alvgren

Original Message:
Sent: Tue November 05, 2019 06:07 AM
From: JANNE LIND
Subject: Problem with Outlook365 and attached Excel-files

Hi Håkan, 

Do you have Scandinavian characters in the report name? One my clients claimed that this was happening on their reports until the Scandinavian characters were removed from the report name. If this is the case and workaround works, I would recommend raising this as support case as it is most likely a bug. 

I hope this helps.

------------------------------
JANNE LIND

Original Message:
Sent: Tue November 05, 2019 02:22 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Hi all,

We have implemented 11.1.4 and suddenly there is a problem with Excel-attachments when e-mails are sent to receivers using Outlook365. When the mail arrives it has an attachment named like "=utf-8BU8OkbGpzdMOkbGxlcmFwcG9ydF9zdi1zZV9J= =utf-8BTkxBTkRTQkFOQU5fb2t0LTIwMTkueGxzeA===" which can't be opened.

When sending the same mail to any other type of mail-system the Excel-file is correctly attached.

What's even more puzzling is that it doesn't happen for all reports, only for some. I found an old page from IBM suggesting to set RSVP.EXCEL.EXCEL_2007_FILE_ZIP to true. This doesn't seem to have any effect anymore judging from looking at the attachment in hex-format.

Has anyone of you seen this and hopefully found a solution?

Best regards


------------------------------
Håkan Alvgren
------------------------------
#CognosAnalyticswithWatson

Just heard from a partner that this has been logged as bug. 

PH18964 SPECIAL CHARACTER IN NAME OF REPORT VIEW WHICH IS SENT AS EMAIL CAUSE UNREADABLE ATTACHMENT

------------------------------
JANNE LIND
------------------------------

Original Message:
Sent: Thu November 07, 2019 11:10 AM
From: Mikko Pietilä
Subject: Problem with Outlook365 and attached Excel-files

Hello all,

I am obviously fighting with the same problem. While testing I have noticed following with names of the reports/report views:

• Report name: "äöå äöå äöå äöå", 15 characters, OK
• Report name: "äöå äöå äöå äöå äöå", 19 characters, FAILED
• Report name: "Kehitysyhteistyömäärärahat", 25 characters, OK
• Report name: "Ministeriön Kehitysyhteistyömäärärahat", 38 characters, FAILED

(yeah, the first two report names are meaningless, even in Finnish ;). 

So report names shorter than 32 character might cause failing also. 

Cheers,

------------------------------
Mikko Pietilä

Original Message:
Sent: Thu November 07, 2019 07:05 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Thanks René,

Yes you are correct, when I look at the failing reports the file name is 32 characters or longer. I have opened a case with IBM and will add this info.

Regards,

------------------------------
Håkan Alvgren

Original Message:
Sent: Thu November 07, 2019 06:03 AM
From: René Kent Nielsen
Subject: Problem with Outlook365 and attached Excel-files

Hi Håkan,

We see the same problems with Outlook365 as the recipients mail program, what we found is if the report name is shorter than 32 characters it seems to go fine with Scandinavian characters.

Br
René

------------------------------
René Kent Nielsen
Solutions Architect
CogniTech A/S
Herning

Original Message:
Sent: Wed November 06, 2019 03:27 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Hi Janne,

You're absolutely correct. I found a couple of problems and I will try to report them:

1) In EventStudio you can't have national characters in the report name or in the burst label if the package comes from Framework Manager. It's strange but it seems to work if the package is a dynamic cube.

2)There seems to be a migration problem for some jobs and then national characters in the report name didn't work. These jobs were identified by having no activities when opened but the showed activities when opened in "Classic view". I had to redo those jobs from scratch and then everything seems to work as expected.

What I still can't understand is why this problem seems to be limited to recipients using Outlook365.

------------------------------
Håkan Alvgren

Original Message:
Sent: Tue November 05, 2019 06:07 AM
From: JANNE LIND
Subject: Problem with Outlook365 and attached Excel-files

Hi Håkan, 

Do you have Scandinavian characters in the report name? One my clients claimed that this was happening on their reports until the Scandinavian characters were removed from the report name. If this is the case and workaround works, I would recommend raising this as support case as it is most likely a bug. 

I hope this helps.

------------------------------
JANNE LIND

Original Message:
Sent: Tue November 05, 2019 02:22 AM
From: Håkan Alvgren
Subject: Problem with Outlook365 and attached Excel-files

Hi all,

We have implemented 11.1.4 and suddenly there is a problem with Excel-attachments when e-mails are sent to receivers using Outlook365. When the mail arrives it has an attachment named like "=utf-8BU8OkbGpzdMOkbGxlcmFwcG9ydF9zdi1zZV9J= =utf-8BTkxBTkRTQkFOQU5fb2t0LTIwMTkueGxzeA===" which can't be opened.

When sending the same mail to any other type of mail-system the Excel-file is correctly attached.

What's even more puzzling is that it doesn't happen for all reports, only for some. I found an old page from IBM suggesting to set RSVP.EXCEL.EXCEL_2007_FILE_ZIP to true. This doesn't seem to have any effect anymore judging from looking at the attachment in hex-format.

Has anyone of you seen this and hopefully found a solution?

Best regards


------------------------------
Håkan Alvgren
------------------------------
#CognosAnalyticswithWatson