cancel
Showing results for 
Search instead for 
Did you mean: 

Field labels in login screen

thies_laemmke
Explorer
0 Kudos

Hi,

I am experiencing strange field labels in the CDT 7.0.8 login screen:

Any suggestions why this is happening?

Thies

Accepted Solutions (1)

Accepted Solutions (1)

former_member158363
Active Contributor
0 Kudos

Hi Thies,

that looks really strange. My first guess would be that your browser is sending language code which is not supported or the text resource file is not found correctly on server.

Did you try to explicitly set your language to English , for instance, in Internet Explorer preferences?

Is this fresh installation or upgrade - if yes, what was your previous version?

I have done 2 upgrades to SP8 recently and it was without any problem.

Regards,

Dawood.

thies_laemmke
Explorer
0 Kudos

Hi Dawood,

the upgrade path was ... -> 6.0.10.0 -> 7.0.7.0 -> 7.0.8.0. The problem started after upgrading from 6.0.9 to 7.0.7.

Thanks for the suggestion with the IE language preference, but languages de, en and da all show this behaviour.

I also checked the TRANSLATOR.TXT file, which is in the Web Clients package, and it contains e.g. the line CDT_XGRP_PASSWORD. This file is also present in WEB_VU\web\cdt.

I am only having the problem in the splashscreen and logon screen during start of CDT. Once CDT is started all is ok.

Any other suggestions?

Thies

former_member158363
Active Contributor
0 Kudos

Hi Thies,

this really looks like some strange language translate problem. The user forces language from his/her user master data record after authentication so therefore it probably works after logon.

Please, how does the splash/logon screen looks like when you try to to run monitor, i.e. http://<VU Website>/monitor? The language for monitor logon is possible to influence by language setting in IA for  VU Website:

Regards,

Dawood.

thies_laemmke
Explorer
0 Kudos

Hi Dawood,

good idea! The first thing I noticed was, that the default language was set to 'english' where as the drop-down list only offered 'English'. However changing the default language to 'English' or 'Danish' didn't make any difference, and the login screen for the Monitor Website shows the same behaviour as CDT:

I can also see, that the /cdt/startpage.htm contains a section of 'default translation items':

But they seem not to be triggered...

Thies

former_member158363
Active Contributor
0 Kudos

Hi Thies,

I believe the startpage.htm is apparently a template, which should be server-parsed by IIS.

I have checked the web page source on client side and all tokens are replaced. I do not think the template contains "default" terms actually - the // just denotes comments.

As I am not expert in IIS, this is what I would do in your place:

1) Double check all prerequisities for your version, especially server roles, features, and .NET libraries. Look into install guide.

2) Check installed files (Differences) (in IA, right click on HAC level).

3) Do you have more application servers? If yes, switch the VU to another instance. If the problem persist, it is a VU content problem. If not, then it is probably IIS setting or instance server environment (see point 1 or 2).

4) If you have only one application server or point 3 indicates VU content problem, then allocate additional vritual IP address and setup new VU Website. Unlike your current one, which contains breadcrumbs of your upgrade path, the new VU Website will be fresh installed from your latest installation package. If it works with second VU, then you are there - you can further investigate by comparing both VUs or simply abandon the first one and be happy with the second one.

5) Create OSS message and supply then SAP with website and CDT logs on trace or debug level.

And of course - backup before playing around .

Just one experience - last year I had problem with VU Integration at one customer - it went up, winked at me with green status for a fraction of second and then it went down - yellow and red crossed. SAP support was not able to find root cause - they adviced to reinstall the VU. This did not help. So I tried to create VU with a different name and everything works fine since then.

Regards,

Dawood.

former_member187604
Contributor
0 Kudos

Lot of good advice already.

One addition: if you have an http proxy, try by-passing it as one test scenario.

BR
-Lasse-

thies_laemmke
Explorer
0 Kudos

Hi Dawood,

Ad 4) solved the problem. I just deployed an additional Web Server VU and now all the labels are visible.

Thank you very much for helping! You are a star

Thies

former_member158363
Active Contributor
0 Kudos

Hi Thies,

thanks for your feedback and acknowledgment .

Thinking back, most issues that I have to solve in CCtr for my customers are somehow related to IIS - either Webclient or Integrations. We have all customers with SAP CRM integrated and IIS is usually a painpoint during patching/upgrading or even during runtime, like switching between instances.

Regards,

Dawood.

reyes_piqueras
Employee
Employee
0 Kudos


Hi Dawood,

Thank yor for providing your helpfull hints.

Regarding IIS troubleshooting, as you have deep knowledge on this area, I encourage you to create an SCN document, similar to this very useful one http://scn.sap.com/docs/DOC-52537 created by Andrei Vishnevsky, which has been viewed 3362 times

Best regards

Reyes

Answers (2)

Answers (2)

alexander_kupke
Participant
0 Kudos

Hi,

I found another way to solve the same issue, at least one that worked for me.

Actually the default language Dawood mentioned seemed to be the culprit in my case.

I also did an update to 7.0.8, but actually we had the issue previously with some earlier 7.0 version in a different installation.

Edit: the wrong small letter Version seems only to show up in systems which had been migrated from BCM 6.0 Installations.

After the update we did not pay attention to the default language which was still the default englisch. And yes, "english" was what was shown in IA within the software parameters.

Checking the drop down list, I found that our english entry with small e sat right at the end, while all other languages had been wirtten with capital letters in front.

As mentioned we didn´t pay attention, but it seems in some place something changed here.

After selecting the new "English" entry and the standard synchronise/apply all variables now showed the correct text during logon.

My guess, decission for language is case sensitive, and with the english entry, simply no language was found andno translation was used. If someone wants to prove, you might want to change the writing of the language name in the translator.txt file and reset the VU, this might bring it back into a working condition as well. At least until the next update.

I guess a new VU installation actually does the same trick, as you would automatically select the capital letter version of the language.

BR

Alexander

former_member158363
Active Contributor
0 Kudos

Hi Alexander,

good job!

With your hint, I was able to reliably reproduce the problem and finally tick off this problem from my head - was like a little worm intruding my sleep .

So how it (probably) works?

The VU Website default language is written into registry key HKLM\SOFTWARE\Wow6432node\Wicom\<VU website name>\WebClient\cdt (among others), with its uppercased code (e.g. CS for Czech, EN for English).

Now the same key is then used for column selection in file <VU websitename>\web\cdt\TRANSLATOR.TXT.

I tried to manually lower case the Default language registry value from "CS" to "cs", restarted the VU and the CDT logon screen was broken - same picture as Thies Laemmke complained.

Then I edited first row of the TRANSLATOR.TXT - found the "CS" column, lower case, saved, restarted the VU - and the CDT screen was fixed.

So it must be probably some leftover of previous versions, as you suggested. I have never came across this problem.

Thanks and regards,

Dawood.


former_member250653
Participant
0 Kudos

Do you have this issue at all clients? Also at clients which didn't use 6.0.10.0 before?

I would try to clear the browser's cache.

BR,

Thomas

thies_laemmke
Explorer
0 Kudos

Hi Thomas,

thanks for the Tip with clearing the browser cache, which unfortunately didn't solve the problem. As we are currently testing the upgrade, I only had three clients I could test with so far. All showed the same behaviour. One was a new install without having an earlier version of CDT installed.

Thies