Hello!
Today, I installed new version 4.1.1.1 of Tamino.
Unfortunately it is a bug in Tamino Manager:
Tamino
Location Management
Add → Browse…
When I chose “browse…” button I got the following error message dialog in my IE browser:
--------------------
“Assertion failed: option.text missing
*** Stacktrace disabled ***”
--------------------
Also I checked in previous 3.1.1.1 version of Tamino, and … it works ok.
What can I do to fix it?
Please help me!
best regards,
Dariusz Baumann
I tried in different way. I copy and paste “path” into “Location Path” so my path is:
C:\Documents and Settings\All Users\Dane aplikacji\Software AG\Tamino
Then I defined “Location Name:” into backup_new and click “OK” button.
Then I got the following error text:
-----------------------
INOAAE0131 Location path C:\Documents and Settings\All Users\Dane aplikacji\Software AG\Tamino includes no valid directory root
-----------------------
I do not really understand why it is not valid directory!
How can I fix it?
Any help will be appreciated.
best regards,
Dariusz Baumann
One recommendation would be to delete everything in the browser cache. It is possible that the Tamino Manager is using parts that are cached from v3.1.1.1 and parts that are not from v4.1.1.
Stuart Fyffe-Collins
Software AG (UK) Ltd.
I have deleted all cache files, however it still does not work, at all.
What can I do to fix it? It is very important for me!
best regards,
Dariusz Baumann
It works for me and in all the Tamino v4 installations I’ve done it’s always worked. So I dunno. If you need a quick solution, please contact your local Software AG customer support and raise the issue with them.
best regards,
Stuart Fyffe-Collins
Software AG (UK) Ltd.
Hello Dariusz,
is your Tamino installed on Windows - and if so, which version (and Service Pack)?
Which version (and SP) of IE are you using?
Have you installed the hotfix that came with Tamino 4.1.1.1 on Windows?
Finally: what type of partition is your “C:\Documents…” directory on - NTFS, FAT32, …?
Thanks,
Trevor.
First of all, it still doesn’t work!
1)
My environement is:
Tamino 4.1.1.1
Windows 2000 Professional with SP3
Internet Explorer 6.0
Type of partition: NTFS
I installed Hot Fix and update Ts41103.exe
2) I made some tests with Tamino Manager and Netscape 7.0, unfortunately the same error appeared like in Internet Explorer 6.0!
Maybe there is the problem with JS scripts located in directory:
C:\Program Files\Software AG\System Management Hub\htmllayer\js
Maybe, there is a bug in gui.js or in other js files ?!!?!
What can I do?
For me, TM in 4.1.1.1 does not work properly with JS scripts.
Please help me!
In advance, thanks a lot.
best regards,
Dariusz Baumann
Hello Dariusz,
which locale are you using with Windows?
Thanks,
Trevor.
I have got:
1. Windows Professional Polish Version.
2. Internet Explorer 6.0 Polish Version
3. Netscape 7.0 English Version
So, what is it the solution for solving this problem?
best regards,
Dariusz Baumann
Hi,
This error popup message you are seeing is not actually a bug in the JavaScript but it means that the data it has recieved is incorrect and as such cannot be displayed correctly.
I suspect that as you are on a Polish machine it may be an issue with an incorrectly handled Polish locale character. Does the path or any of its files/subdirectories contain any non ASCII characters ? If so does this error message go away if you use a directory and path with only ASCII characters in it ?
Thanks,
Andrew Hodgetts.
Software AG(UK)
Hi,
the SAG support is already taking care of this and those obviously related problems Dariusz reported. It seems, that the problems are special cases, because it is not possible for me to reproduce them.
So you should (keep) contact with SAG support.
Regards,
Uli
[This message was edited by Uli Faltermann on 14 Feb 2003 at 15:56.]
Hello Dariusz,
I have also tried - but failed - to reproduce the problem. I tried switching to the “Thai” locale (as I did not find Polish in the list of locales!), but this was not sufficient. IE switches the locale to US English when I start the SMH.
Do you have access to a Windows installation which is using one of the langauges/locales in the list from the other posting?
Perhaps this could be a temporary workaround for you whilst Support resolves the issue.
Greetings,
Trevor.