on 07-29-2015 9:19 AM
Today is a day when Windows 10 arrives and customers will start upgrading their PC-s.
Has anyone already tested it? Will SAP CCtr run on Windows 10.
Hi guys,
I have created KBA 2315845 for this issue.
Please check what windows time setting you are using. And also check CDT log to see if there's error like mentioned in this KBA note. If so, please follow the KBA.
Best Regards,
James Chi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi James Chi,
Thank you very much for the note and advice!
It was very helpful.
The easiest fix was through regedit.
HKEY_CURRENT_USER\Control Panel\International\sTimeFormat
There was a dot instead of a colon before seconds.
I replaced it with colon and all works.
Here:
Checked the CDT logs again and it is now clean from errors as well.
Great!
Best regards,
Roman
Thanks James!
For anyone coming across this issue, you could add (either here or in your support incident) some of the related error lines
[dispatchEventCDT.jsc] [ERR] getCurrent...
[calendar.htm] [ERR] fParseDate...
from your CDT log, together with information about your date and time locale settings, as examples.
BR
-Lasse
07:40:19.093 | [dispatchEventCDT.jsc] | [ERR] | getCurrent -> Time delimiter (:) mismatch with time format (H:mm.ss) | 0 |
07:40:19.095 | [dispatchEventCDT.jsc] | [ERR] | getCurrent -> Time delimiter (:) mismatch with time format (H:mm.ss) | 0 |
07:40:19.097 | [dispatchEventCDT.jsc] | [ERR] | getCurrent -> Time delimiter (:) mismatch with time format (H:mm.ss) | 0 |
07:40:19.828 | [dispatchEventCDT.jsc] | [ERR] | getCurrent -> Time delimiter (:) mismatch with time format (H:mm.ss) | 0 |
Hi Roman,
Do you have any idea why there were a dot in that field? I'm asking to understand how widely spread this issue is. As far as I know the values are goming from regional settings, which are maintained by Microsoft.
Can you check what region settings are in use? I could then check if the same can be reproduced here and maybe see how many regions has the same.
Regards,
Jukka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi guys,
A big thank you goes to James and Roman!
My computer has the same configuration as Roman's - Win10 Pro with default language of English(United States) and default region of Estonia.
I tried Roman's quick-fix of altering sTimeFormat value but it didn't work for me.
So I changed my region to United States and tried CDT - all the dates and times were visible.
Then i changed the region back to Estonian and altered the time format manually from H:mm.ss to H:mm:ss.
After that all the dates and times were visible.
Thanks again!
Erik
Hi Guys,
short update around the topic: we are going to test Win10 + IE combination in SP9 test plan. So, we are planning to add support to coming SP9 release. Of course if there is major findings we might have to postpone the support release.
Regards,
Jukka
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Jukka!
Among our customers we have at least few hundred PC-s that have been upgraded to windows 10.
Although it runs stable the notable problem we have seen is with dates in CDT.
For example in History Search the date range calendar is not working, so you have to insert the digits manually and also when you open an item in History then arrival time field is empty.
Best regards
Roman
Very good information. Thank you!
I quickly tested the mentioned problem points and:
date range & calendar: opens fine, but to wrong place.
time field is empty: also this seems to work nicely in my enviroment.
Could you share screenshots from these? Just checking that we are speaking about the same fields?
Regards,
Jukka
Hi Guys,
at the moment I don't have ETA for Windows 10 support to give. But we are anyhow speaking about some future service pack. SP9 might come too soon and I would say that SP10 is more realistic option. Please note that this is not an promise but only an early guess.
Meanwhile would be nice to hear how many of your customers has started upgrade project? From the history we have seen that customer are not too eager to upgrade immidiatly after release. Usually it takes half a year of one year before there is real demand.
Regards,
Jukka
SAP Contact Center team
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Jukka,
just a question that is related to this topic also it is kind of a sidetrack at the moment.
As IE 11 is available for Windows 10 (btw. we found installations having it not installed by default but that required installing it separately) I do not see immediate issues with Windows 10 and CDT not getting along.
But to my knowledge, IE 11 is provided as a legacy software to serve compatibility issues only and except for security fixes I was told no further development is planned. The new default browser is supposed to be Microsoft Edge which will be developed from here. (EOL for pre IE 11 versions is January 12. 2016)
Main issue at the moment for SAP Contact Center, Edge no longer supports ActiveX as this is declared a deprecated technology by Microsoft itself.
Are there already plans on what could come next as a client? As to know a CDT based on ActiveX components seems to be a feasible way to go only for a certain time to come. (No, not an immediate issue, but as time goes by...)
BR
Alexander
Hi Alexander
You bring up a valid point.
I am confident product management will communicate about the future plans in due course..
As to the IE 11 and WIndows 10 concerns, Microsoft has e.g. the following resources:
BR
-Lasse
Hi Roman,
I upgraded a Windows 7 Pro computer to Windows 10 Pro N today. IE11 is still a part of it and you can start CDT (7.0.8.102). CDT seems to function as well. However until SAP puts Windows 10 on the list of supported OS, I guess you cannot be sure that it functions correctly, and I guess there is no help to get at SAP if it doesn't.
Thies
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
8 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.