RE: (forte-users) Auto Login...

Hi Craig,
Please look at the Technote 11545. If you want to use a User Visible SO and
make it available to other SO or clients you have only 3 choices:
* using an agent
* using BindObject
* using reference partition
Solutions and "How to" you can find in this Technote.
Regards,
Zenon Adamek
Purolator
-----Original Message-----
From: Craig Muir [SMTP:craig.muirstonebow.otago.ac.nz]
Sent: Monday, June 19, 2000 7:53 PM
To: kamranaminyahoo.com
Subject: (forte-users) Auto Login...
Hi.
I want to update our login window so a user only has to manually log in
once, regardless of what applications they run.
Currently, whenever a user wants to run an app, they have to log in
manually.
If they already have 3 aps running on their machine under the same
usercode, they still have to enter their usercode and password. Given the
environment our users work in, this is somewhat redundant, since they will
invariably be logging in under the same usercode, and therefore the same
password, every time.
Basically, I want a user to login as usual (manually) when they have no
apps running.
Then, while they have any apps running, I want them to be able to start
any
other app they have rights to without having to type their details in
again. I still want the same security as if they were logging in manually,
I just want the login details for the new app to be retrieved from the
open
app (same usercode) and the login done behind the scenes, so to speak.
If at any time they try to open an app and they don't already have one
running, they get the usual login screen.
So far, my idea is to have a SO on the client as a separate task and
manage
it using a systemAgent. The SO would hold the usercode, and what apps the
user is running. This would be polled to get the relevant usercode for
login to happen invisibly to the user. When a new app is started, it is
added to the list, when it's killed, it gets removed, etc. Once the last
one is removed, kill the SO task.
Does Forte have a more direct way to do this?
Surely someone has done this already?
Does this approach work?
Any help would be great.
Thanks.
Craig.
Craig Muir Administrative Technology Services
Analyst Programmer University of Otago
Dunedin, New Zealand
Ph: +64 3 479 5144
Fax +64 3 479 5080 mailto:craig.muirstonebow.otago.ac.nz
-> You don't stop laughing because you grow old;
-> you grow old when you stop laughing.
For the archives, go to: http://lists.xpedior.com/forte-users and use
the login: forte and the password: archive. To unsubscribe, send in a new
email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

Et voilà,
WindowsUserName : TextData;
WindowsUserName = task.part.OperatingSystem.GetEnv(name='username');
Hope this helps
Fabrizio Genesio
Datasign AG für Informatik
ch. d'Eysins 53a
CH-1260 Nyon
Switzerland
Tel.: +41 22 361 04 04
Fax: +41 22 361 01 10
e-mail: fabrizio.genesiodatasign.ch
<mailto:fabrizio.genesiodatasign.ch>
URL: www.datasign.ch <http://www.datasign.ch>
-----Original Message-----
From: Olivier Andrieux [SMTP:oandrieuxaxialog.fr]
Sent: Thursday, 27 April 2000 11:53
To: Mailing Liste Forte
Subject: (forte-users) a french question about a login
Bonjour,
J'ai une petite question &agrave; vous soumettre:
Je voudrais r&eacute;aliser une fen&ecirc;tre de login avec Fort&eacute;, mais pour
cela il me faudrait r&eacute;cup&eacute;rer les informations
d'identification de chaque utilisateur sur le serveur
NT. Questionner le serveur en utilisant les m&ecirc;mes noms et mots de passe
utilisateurs que le serveur.
Cela est-il possible ?
Je vous remercie par avance pour vos r&eacute;ponse .
A bient&ocirc;t
Olivier.
Olivier Andrieux
Axialog Lille
France

Similar Messages

  • How to auto login multiple users on boot?

    I have mac mini and have users with autostart some programs. But autostart is only when i login on this account.
    So now only i can login in to each account and when switch to next account. But it is not good.
    I need auto login in to all needed user account. How do that?

    Yeah, I'm a big believer in just keeping the machine running, but unfortunately the machine ends up freezing up a few times a month and then it hours of agony as the family complains they can't log into their accounts..etc. I'm going to try updating the hard drive to one of the new Seagate Hybride SSD/HDD drives to help speed the machine up overall. No worries, I've been cleaning off the machine trying to make it run a little smoother (2011 iMac 27", 16GB Ram, 2.97 i7) until I can get a new machine that's a little beffier (the new Mac Pro let's just say).

  • Auto-login then Fast User Switch out?

    I've got a few programs (e.g. Chronosync) that need to launch as a user upon login. I need these to launch at boot time. Of course, I could auto-login to this account, but that would leave the machine sitting there with an admin account logged in (something I'd rather not do).
    Is there any way I could do something like auto-login to this acct at boot and then do an immediate FUS out to the login window?
    Craig

    One way to do this is with Automator:
    1) Launch Automator. Make a new custom workflow.
    2) Choose the "run shell script" action. Paste this text into the box:
    /System/Library/CoreServices/Menu\ Extras/User.menu/Contents/Resources/CGSession -suspend (all that should be on one line)
    3) Save the workflow as an application.
    4) Go to System Preferences -> Accounts -> your account -> Login items. Make your Automator app a login item.

  • How to hide user id and password for auto login in Analyzer 6.5?

    Could anyone tell me is it possible to hide the user id and password for auto login in Analyzer version 6.5 and how?Thanks in advance...

    Sainath,
    Referring admin guide as mentioned by Craig is good option.
    Let me give you few steps that I did in one of my projects.
    Open command prompt and navigate to the path "C:\Oracle\Middleware\EPMSystem11R1\products\DataRelationshipManagement\client\batch-client".. here you can see many see other utilities as well.
    drm-batch-client-credentials.exe is the one used to encrypt the userid and password.
    open this in command prompt and then choose the application to which you want to encrypt the password.
    then remove userid and password from batch script then run it... it does what you want

  • Auto login after new user registration

    Hello,
    I would like to go directly to a restricted page (add session variables for username, level, etc) after a new user is registered, without first going to the login page. Is there a way to do this? I tried adding a login user behavior to my new user registration page, but it disabled the form validation on the page. I also tried copying some of the login page code (login transactions) into the new user registration page, but that didn't work either... any help would be greatly appreciated!
    Steve
    BTW, I am not utilizing email activation

    Well I finally figured out a work around... I am sure others will run into this problem and if someone can explain it to me I would be happy. But for now this will work.
    The above code that Steve U posted works for me exactly 50% of the time. It will work every other time, why I don't know. I even changed all of my temp and session directories in php configuration, changed from php5 to php4 and still no fix.
    Here is what I did to get it to work:
    On your registration form underneath the insert transaction you copy and paste the login transaction (that you generate on a login page).
    *Change tNG_login(this is your server connection)
    *Change the POST value to match your submit button on your registration form, mine is KT_Insert1.
    *Modify the redirect trigger to go to the page you want to redirect to after registration.
    *Change the kt_login_user and kt_login_password addColumn values to match the username and password fields in your registration form, mine are email_usr and password_usr
    *comment out the kt_login_rememberme addColumn (or if you need this, modify the code to allow for it in the registration form)
    I have now successfully registered a new account and had it auto-login to the user protected area 10 times in a row now, so this should be working.
    If you want some sample code here it is:
    // Make a login transaction instance
    $loginTransaction = new tNG_login($conn_connection);
    $tNGs->addTransaction($loginTransaction);
    // Register triggers
    $loginTransaction->registerTrigger("STARTER", "Trigger_Default_Starter", 1, "POST", "KT_Insert1");
    //$loginTransaction->registerTrigger("BEFORE", "Trigger_Default_FormValidation", 10, $formValidation);
    $loginTransaction->registerTrigger("END", "Trigger_Default_Redirect", 99, "user/confirmlogin.php");
    // Add columns
    $loginTransaction->addColumn("kt_login_user", "STRING_TYPE", "POST", "email_usr");
    $loginTransaction->addColumn("kt_login_password", "STRING_TYPE", "POST", "password_usr");
    //$loginTransaction->addColumn("kt_login_rememberme", "CHECKBOX_1_0_TYPE", "POST", "kt_login_rememberme", "0");
    // End of login transaction instance

  • Auto-Login Network User

    I am wondering if there is any way to auto-login as a network user?

    Quit System Preferences.
    Go to Finder and select your user/home folder. With that Finder window as the front window, either select Finder/View/Show View options or go command - J.  When the View options opens, check ’Show Library Folder’. That should make your user library folder visible in your user/home folder.  Select Library. Then go to Preferences/com.apple.systempreferences.plist. Move the .plist to your desktop.
    Restart, open the System Preferences and test. If it works okay, delete the plist from the desktop.
    If the application is the same, return the .plist to where you got it from, overwriting the newer one.
    Thanks to leonie for some information contained in this.

  • Deploy an auto-login user on 10.9.5

    I am trying to create an auto-login user on our network of 10.9.5 machines, but the com.apple.loginwindow.plist reverts itself after any change I make (I have tried changing it in terminal and editing it manually). I understand that starting with Mavericks that plist files are now cached, and I believe that this has something to do with it. Has anyone been able to implement auto-login network wide on 10.9.5?

    Quit System Preferences.
    Go to Finder and select your user/home folder. With that Finder window as the front window, either select Finder/View/Show View options or go command - J.  When the View options opens, check ’Show Library Folder’. That should make your user library folder visible in your user/home folder.  Select Library. Then go to Preferences/com.apple.systempreferences.plist. Move the .plist to your desktop.
    Restart, open the System Preferences and test. If it works okay, delete the plist from the desktop.
    If the application is the same, return the .plist to where you got it from, overwriting the newer one.
    Thanks to leonie for some information contained in this.

  • RE: (forte-users) Terminal Services - Win 2000

    Hi
    l've already installed my application 'appA' at my server 'ServerA'.
    When l try to execute this application in my pc thru Terminal Server, there
    were nothing displayed at my pc but when l check at on 'ServerA' , l can
    see that 'appA' is running over at the 'ServerA' side. Actually, I'm new at
    this Terminal Server thingy...
    thanks..
    -----Original Message-----
    From: Jean-Paul Gabrielli [mailto:Jean-Paul.Gabriellisema.fr]
    Sent: Friday, January 19, 2001 5:08 PM
    To: Zulkifli Mohamad
    Subject: RE: (forte-users) Terminal Services - Win 2000
    hmm when you telent a machine to run a process remotely, don't expect to
    have it locally :-)
    j-p
    -----Message d'origine-----
    De: Zulkifli Mohamad [mailto:zulkifli_mohamadkonnas.com.my]
    Date: vendredi 19 janvier 2001 09:19
    &Agrave;: forte-userslists.xpedior.com
    Objet: (forte-users) Terminal Services - Win 2000
    hi..
    l'm trying to run forte application thru Terminal Services Client
    (Win 2000) but my application only running on the server not at the client
    pc. Some one can help me...
    thanks.
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

    Il suffit de mettre les BTD/BTX sur un drive r&eacute;seau (net use X:
    \\server\share_point),
    puis d'installer des ic&ocirc;nes pour les clients: ftexec -fi bt:x:\MyApp.
    Pour que les noeuds ne s'auto-enregistrent pas, peut-&ecirc;tre mettre un password
    Ou bien d&eacute;finir les noeuds comme un 'groupe' et donc seul le groupe est
    connu.
    Si mettre le mot de passe suffit pas, et si vraiment le model node g&ecirc;ne,
    alors il
    faut un autre environment manager.
    I think that to avoid install, the software could be located on a shared
    drive,
    and users linking to it through running 'ftexec' or directly the compiled
    binaries.
    For nodes not to appear in the environment as nodes, they could be defined
    as members
    of a model node '(which then would be in the environmnet)'
    Putting a password in the environment could prevent nodes to be registered
    there, but
    might prevent the apps from being executed.
    Cheers,
    j-paul gabrielli
    Sema DTS
    -----Message d'origine-----
    De: Thomas Felix [mailto:tfelixaxialog.fr]
    Date: mardi 2 mai 2000 14:14
    &Agrave;: forte-userslists.xpedior.com
    Objet: (forte-users)
    bonjour a tous
    je souhaites installer une application distribu&eacute;e sur des postes clients.
    Y'a t'il moyen de ne pas installer les noeuds de ces postes clients sur l'
    active environnement li&eacute; au d&eacute;veloppement et si oui comment?
    hi
    I would like to install an application on clients workstation
    Can i install this nodes in a different Active environnement than this one
    that we use for the developpement ?
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

  • RE: (forte-users) Killing the Nones - solved

    Thanks to all of you who helped ... this pex file works great.
    Allan
    -----Original Message-----
    From: kelsey.petrychynsasktel.sk.ca [SMTP:kelsey.petrychynsasktel.sk.ca]
    Sent: Thursday, August 24, 2000 9:51 AM
    To: Pomeroy, Allan
    Cc: kamranaminyahoo.com
    Subject: Re: (forte-users) Killing the Nones
    Try the code contained in this pex file.
    We got it from someone in Forte quite a while ago and found that it worked
    pretty good. I haven't used it for a long time since, and it was probably
    written using an old version of Forte. However, it should still work, or
    at
    least you may find some salvageable code that can be "modernized" to what
    ever
    version you are using.
    (See attached file: FtExecShutDown.pex)
    PS
    You would almost think that by version 3+ of a product Forte would have
    nailed
    down their empty and orphaned (defunct in UNIX) processes bugs. The
    environment
    manager should be able to auto-magically shut them down or at least keep
    them
    down to an acceptable number. But alas, we still find ourselves
    occasionally
    exceeding our finite server resources due to rouge processes doing
    nothing.
    Kelsey PetrychynSaskTel Technical Analyst
    ITM - Technology Solutions - Distributed Computing
    Tel (306) 777 - 4906, Fax (306) 359 - 0857
    Internet:kelsey.petrychynSasktel.sk.ca
    Quality is not job 1. It is the only job!
    "Pomeroy, Allan" <Allan.PomeroyLibertyMutual.com> on 08/24/2000 07:09:16
    AM
    To: kamranaminyahoo.com
    cc: (bcc: Kelsey Petrychyn/SaskTel/CA)
    Subject: (forte-users) Killing the Nones
    Venerable Forte Gurus,
    Aside from using the Econsole, is there a way to kill the "None" ftexecs
    that sometimes hang around after forte partitions are shut down?
    In Econsole, if you view->node outline, then select the Forte Executor,
    you
    may see some running ftexecs with no application assigned -- they show up
    as
    "None". When I subsequently launch applications, I want them to start in
    new ftexecs, not in the old "none"s, which have old command-line parms,
    memory settings, etc.
    Thanks!
    Allan
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com
    << File: FtExecShutDown.pex >>

    Try the code contained in this pex file.
    We got it from someone in Forte quite a while ago and found that it worked
    pretty good. I haven't used it for a long time since, and it was probably
    written using an old version of Forte. However, it should still work, or at
    least you may find some salvageable code that can be "modernized" to what ever
    version you are using.
    (See attached file: FtExecShutDown.pex)
    PS
    You would almost think that by version 3+ of a product Forte would have nailed
    down their empty and orphaned (defunct in UNIX) processes bugs. The environment
    manager should be able to auto-magically shut them down or at least keep them
    down to an acceptable number. But alas, we still find ourselves occasionally
    exceeding our finite server resources due to rouge processes doing nothing.
    Kelsey PetrychynSaskTel Technical Analyst
    ITM - Technology Solutions - Distributed Computing
    Tel (306) 777 - 4906, Fax (306) 359 - 0857
    Internet:kelsey.petrychynSasktel.sk.ca
    Quality is not job 1. It is the only job!
    "Pomeroy, Allan" <Allan.PomeroyLibertyMutual.com> on 08/24/2000 07:09:16 AM
    To: kamranaminyahoo.com
    cc: (bcc: Kelsey Petrychyn/SaskTel/CA)
    Subject: (forte-users) Killing the Nones
    Venerable Forte Gurus,
    Aside from using the Econsole, is there a way to kill the "None" ftexecs
    that sometimes hang around after forte partitions are shut down?
    In Econsole, if you view->node outline, then select the Forte Executor, you
    may see some running ftexecs with no application assigned -- they show up as
    "None". When I subsequently launch applications, I want them to start in
    new ftexecs, not in the old "none"s, which have old command-line parms,
    memory settings, etc.
    Thanks!
    Allan
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

  • RE: (forte-users) R: (forte-users) ASP andForté

    I think you should also be able to publish the Forte Service Objects as DCOM
    services. Then you can access them from within VB-scripts.
    Pascal Rottier
    Atos Origin Nederland (BAS/West End User Computing)
    Tel. +31 (0)10-2661223
    Fax. +31 (0)10-2661199
    E-mail: Pascal.Rottiernl.origin-it.com
    ++++++++++++++++++++++++++++
    Philip Morris (Afd. MIS)
    Tel. +31 (0)164-295149
    Fax. +31 (0)164-294444
    E-mail: Rottier.Pascalpmintl.ch
    -----Original Message-----
    From: Massimiliano Delsante [mailto:delsanteotconsulting.com]
    Sent: Friday, February 23, 2001 9:54 AM
    To: BOLIVARD Kenny; forte-userslists.xpedior.com
    Subject: (forte-users) R: (forte-users) ASP and Fort&eacute;
    Hi Kenny,
    I suggest you to use XML in order to publish your Fort&eacute; services.
    There is a Fort&eacute; Library called HTTPDC that let you start up a listener that
    answer to HTTP Request.
    So you will have a ASP/Fort&eacute; integration via HTTP/XML
    Hope this helps.
    ----- Original Message -----
    From: BOLIVARD Kenny <BOLIVARDPREVIADE.FR>
    To: <forte-userslists.xpedior.com>
    Sent: Friday, February 23, 2001 8:43 AM
    Subject: (forte-users) ASP and Fort&eacute;
    Hi everybody!
    I'm a new Fort&eacute; developer, so i have some question about it, speciallyone:
    I want to access Fort&eacute; service objects through an ASP script. To be more
    precise, I want to get back some informations (like, for exemple, the
    information of a customer's account) from the Fort&eacute; world and to make-upthe
    web page in my ASP script.
    Is it possible writing an ASP script (in VisualBasic for example) witch
    calls Fort&eacute; service objects?
    How can I do that? Maybe by using Web Enterprise's libraries, but itseems
    to me that Web access service objet returns only HTLM pages.
    Any suggestions and explanations would be appreciated.
    Thank's in advance for your replies,
    Kenny,
    PREVIADE.
    France.
    Ps: Sorry for my bad english. ;))
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

    Il suffit de mettre les BTD/BTX sur un drive r&eacute;seau (net use X:
    \\server\share_point),
    puis d'installer des ic&ocirc;nes pour les clients: ftexec -fi bt:x:\MyApp.
    Pour que les noeuds ne s'auto-enregistrent pas, peut-&ecirc;tre mettre un password
    Ou bien d&eacute;finir les noeuds comme un 'groupe' et donc seul le groupe est
    connu.
    Si mettre le mot de passe suffit pas, et si vraiment le model node g&ecirc;ne,
    alors il
    faut un autre environment manager.
    I think that to avoid install, the software could be located on a shared
    drive,
    and users linking to it through running 'ftexec' or directly the compiled
    binaries.
    For nodes not to appear in the environment as nodes, they could be defined
    as members
    of a model node '(which then would be in the environmnet)'
    Putting a password in the environment could prevent nodes to be registered
    there, but
    might prevent the apps from being executed.
    Cheers,
    j-paul gabrielli
    Sema DTS
    -----Message d'origine-----
    De: Thomas Felix [mailto:tfelixaxialog.fr]
    Date: mardi 2 mai 2000 14:14
    &Agrave;: forte-userslists.xpedior.com
    Objet: (forte-users)
    bonjour a tous
    je souhaites installer une application distribu&eacute;e sur des postes clients.
    Y'a t'il moyen de ne pas installer les noeuds de ces postes clients sur l'
    active environnement li&eacute; au d&eacute;veloppement et si oui comment?
    hi
    I would like to install an application on clients workstation
    Can i install this nodes in a different Active environnement than this one
    that we use for the developpement ?
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

  • RE: (forte-users) Check this ( -----THIS MESSAGE WASA VIRUS!!!!!)

    The previous message (Check this) is a known virus.
    (Either that or the sender is emulating it.
    Either way, do not open the attachment as you will not have "fun" at all.
    Delete the message immediately.
    Of course, if I am wrong then I am an idiot!
    Don't take the chance.
    -----Original Message-----
    From: Slabbert, Etienne [mailto:etiennemds.co.za]
    Sent: Friday, 18 February 2000 0:12
    To: forte-userslists.xpedior.com
    Subject: (forte-users) Check this
    Have fun with these links.
    Bye.

    Il suffit de mettre les BTD/BTX sur un drive r&eacute;seau (net use X:
    \\server\share_point),
    puis d'installer des ic&ocirc;nes pour les clients: ftexec -fi bt:x:\MyApp.
    Pour que les noeuds ne s'auto-enregistrent pas, peut-&ecirc;tre mettre un password
    Ou bien d&eacute;finir les noeuds comme un 'groupe' et donc seul le groupe est
    connu.
    Si mettre le mot de passe suffit pas, et si vraiment le model node g&ecirc;ne,
    alors il
    faut un autre environment manager.
    I think that to avoid install, the software could be located on a shared
    drive,
    and users linking to it through running 'ftexec' or directly the compiled
    binaries.
    For nodes not to appear in the environment as nodes, they could be defined
    as members
    of a model node '(which then would be in the environmnet)'
    Putting a password in the environment could prevent nodes to be registered
    there, but
    might prevent the apps from being executed.
    Cheers,
    j-paul gabrielli
    Sema DTS
    -----Message d'origine-----
    De: Thomas Felix [mailto:tfelixaxialog.fr]
    Date: mardi 2 mai 2000 14:14
    &Agrave;: forte-userslists.xpedior.com
    Objet: (forte-users)
    bonjour a tous
    je souhaites installer une application distribu&eacute;e sur des postes clients.
    Y'a t'il moyen de ne pas installer les noeuds de ces postes clients sur l'
    active environnement li&eacute; au d&eacute;veloppement et si oui comment?
    hi
    I would like to install an application on clients workstation
    Can i install this nodes in a different Active environnement than this one
    that we use for the developpement ?
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

  • Re: [forte-users] fcompile

    fcompile is a simple utility that operates locally in the current node, and
    does not even require an environment manager to run. It reads the .pgf or
    .lgf file, generates the C++ code and a .bom (bill of materials) file, and
    runs the compcomp script to invoke the compiler. It has no awareness of
    the actual location of the distribution, or of the other nodes in the
    environment. The C++ code generator is 'built-in'.
    makeappdistrib must communicate with the environment manager to store the
    distribution information in the environment repository. During
    makeappdistrib processing of a compile partition, a code generation
    partition is auto-started, and used to generate the C++ code.
    It is the same code generator in both cases.
    -tdc
    iIS Engineering
    At 01:47 PM 5/25/01 -0700, Jeff Bennett wrote:
    All,
    Does anyone know why the MakeAppDistrib with the autocompile set will
    automatically distribute the client for compilation to the proper client node,
    but when I try to recompile the client using fcompile on the server, it does
    not? It simply performs the compile on the server, not the client node.
    -jeff
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: [email protected]

    In a message dated Fri, 25 May 2001 5:20:57 PM Eastern Daylight Time, "Jeff Bennett" <[email protected]> writes:
    <<
    All,
    Does anyone know why the MakeAppDistrib with the autocompile set will
    automatically distribute the client for compilation to the proper client node,
    but when I try to recompile the client using fcompile on the server, it does
    not? It simply performs the compile on the server, not the client node.
    -jeff
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: [email protected]
    >>
    Jeff,
    fcompile is a local utility. It does not have distributed capabilities.
    You can however manually ftp the .pgf file to a client machine. Then you can run fcompile on the client to compile the client partition.
    Andy

  • Auto login in Solaris 10

    Hi all
    I'm trying to establish auto login in Solaris 10, as a regular user or root. This is a personal testing machine, so security is not an issue.
    I want to automatically login preferably in the shell mode, ( no GUI if it's possible ), otherwise I can login with GUI, no biggie.
    From what I've found, it does not seem an easy job, given that my Solaris experience is somewhat limited, ( been working more on Linux ).
    If I can get that going, I'd prefer to run a few scripts upon login, which I think I can do it.
    So what steps must I go through to have auto login upon boot ? How hard is it ?
    Appreciate any comments. Thanks
    PS. Reposted, because I submitted my query in the wrong forum.
    Add the line below, to */etc/inittab* file.
    ip:1234:once:/full/path/to/scriptEdited by: mysol on Aug 4, 2009 4:12 PM
    Edited by: mysol on Aug 4, 2009 4:15 PM

    What do you mean by auto login?
    Do you want to implement Integrated windows authentication in OIM Design console. If yes, then I don't think it's possible.
    Post your requirement here so that ppl can help you out.

  • RE: (forte-users) 3J= 3M new to me error

    Hi Thomas,
    Thanks for your email but I think it will be interesting for Brenda not me.
    It is exactly what I have expected from Forte Support: detailed information
    about bugs and workarounds. But what I cannot understand is that #53398 was
    released without any information about possible reasons for this problem or
    suggested workarounds. My first reaction after reading this bugreport was to
    open a new case at CallCenter to get more information about it. Please
    release more information with your bug reports !
    Regards
    Zenon Adamek
    Information Services
    Senior Programmer Analyst
    Tel: 905 712-1084 ext. 3628
    Fax: 905 712-6709
    E-mail: zadamekpurolator.com
    -----Original Message-----
    From: Thomas Degen - Sun Germany Forte Tools - Bonn
    [SMTP:thomas.degensun.com]
    Sent: Wednesday, September 27, 2000 9:49 AM
    To: Adamek, Zenon
    Cc: 'Brenda Cumming'; Forte-userslists.xpedior.com
    Subject: RE: (forte-users) 3J=>3M new to me error
    Hi Zenon,
    bug #53398 is not a bug which will likely get fixed, it's an informational
    bugreport.
    You might see an errorstack like Brenda has reported (and described in
    informational
    bugreport #53398) probably when you are doing something illegal that is
    possible
    via Forte Tool but Forte is not trapping it for performance reasons. Hence
    you will see
    the error coming from your illegal operation only at runtime, probably
    only
    while
    running interpreted in the Forte IDE, but in worst case it might be even a
    segmentation
    violation.
    Technotes 12448 'Sudden client partition crashes at runtime' and 11225
    'Don't reparent
    mapped Widgets between UserWindows at runtime' explain this matter . See
    attached.
    But maybe Brenda is much more experiencing a problem as described by Forte
    Technote 11398 'Read Only Workspace Errors using ListViews or ActiveX
    control'
    that might get easily resolved via setting of FORTE_YIELD_THROTTLE=0.
    Good Luck and Best Regards !
    BTW: I've logged bug #53398, so I've felt responsible to explain its real
    background.
    Thomas
    Thomas Degen
    Sun Microsystems - Forte Tools
    Forte CTE & Sustaining Group
    Technical Support Germany
    tel.:+49.228/91499-50
    MailTo:thomas.degensun.com
    Technote 11398 Read Only Workspace Errors using ListViews or ActiveX
    control
    SCENARIO:
    Getting some unusual interpreter errors that result in an error stating
    that
    the workspace has been set to read only. Please see Enclosures for the
    two
    most common error stacks that have been encountered. The abbreviated
    versions of the errors are:
    - Can't read record (record size = -1)
    - Id in index does not match id in record header in data file
    - Recursive deserialization attempted.
    - Unknown Mark type in deserialization
    - Could not read record (64,74615) from repository data file.
    Header
    is corrupt.
    These errors can be happening in either the development environment when
    running from one of the development workshops, or with the deployed
    application.
    The bug outlined in this Technote may be the culprit if the errors above
    are
    seen when running a client on Windows NT or Motif and the user interface
    incorporates ActiveX controls or ListView/TreeView widgets.
    CAUSE:
    Basically what is happening is that in rare circumstances Forte may invoke
    a
    nested copy of the interpreter while the first interpreter has yielded.
    This
    is not a problem in and of itself, but in the case where the original
    interpreter was in the middle of a repository fetch when it yielded, and
    the second interpreter needs to fetch code as well, we will get one of the
    errors listed above, depending on the exact timing. The reason for the
    errors is that the repository code at this level is thread-safe but not
    re-entrant. It is protected by a mutex that is already owned by the
    current task. Which, given the scenario outlined here, where the two
    interpreters are running inside of the same task, results in the nested
    interpreter being allowed to change data out from under the first.
    While for every fetch one or more calls to WindowSystem.Yield will be made
    (this is there to prevent the semblance of system lock-up on Win 3.1,
    where
    Yield is the only way other applications can be allowed to run), there is
    a parameter which controls how often to actually yield, which by default
    is
    set to one out of every 100 calls. This is the reason the problem is
    intermittent--you need a yield to occur during a repository fetch
    which starts another interpreter which also needs to fetch code from
    disk.
    The reason this has only surfaced recently is that the nested interpreter
    scenario can only happen in 2 cases that we know of:
    - ActiveX controls which respond to events/Windows messages
    - Outline fields/ListViews with column(s) mapped to virtual
    attributes
    In all other normal cases, the yield can process the message (typically a
    paint message) without starting another interpreter, so regardless of
    whether
    the first interpreter yielded during a repository operation or not, there
    is
    no conflict.
    SOLUTION:
    The workaround is to prevent yields altogether by setting the
    FORTE_YIELD_THROTTLE environment variable equal to 0 in the client's
    environment. This should have no detrimental effects since the yield code
    is in place solely for Windows 3.1x clients.
    ERROR STACK 1
    SYSTEM ERROR: Because of a prior error, your workspace was set to
    read-only to
    prevent the application from attempting to write to the repository. The
    repository and work you have saved to the repository are safe. If your
    workspace
    contains unsaved work, you may use the following procedure to save this
    work.
    First, export the changed components. Then, shut down and restart this
    application and reopen this workspace in read-write mode. Finally, import
    the
    changed components and save your workspace.
    Class: qqrp_RepResourceException
    Error #: [1101, 695]
    Detected at: qqrp_Session::GetObjectById
    Last TOOL statement: method EFWindowController.EFEventLoop
    Error Time: Tue Nov 18 15:58:47
    Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
    (partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
    taskId =
    [7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
    "ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
    The remainder of the Error Manager stack is:
    SYSTEM ERROR: Internal Error attempting to deserialize element (64,67470)
    (fetch
    bitmask is 0x20). Your workspace is now read-only to prevent the
    application
    from attempting to write to the repository. The repository and work you
    have
    saved to the repository are safe. If your workspace contains unsaved work,
    you
    may use the following procedure to save this work. First, export the
    changed
    components. Then, shut down and restart this application and reopen this
    workspace in read-write mode. Finally, import the changed components and
    save
    your workspace.
    Class: qqrp_RepResourceException
    Error #: [1101, 61]
    Detected at: qqrp_LogicalSession::MaterializeObject
    Last TOOL statement: method EFTabManagerNew.EFNoteBookHandler
    Error Time: Tue Nov 18 15:58:47
    Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
    (partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
    taskId =
    [7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
    "ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
    SYSTEM ERROR: Unknown Mark type in deserialization.
    Class: qqsp_ImplementationException
    Error #: [1101, 34]
    Detected at: qqrp_DeSerializeObject::ProcessHdr
    Error Time: Tue Nov 18 15:58:47
    Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
    (partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
    taskId =
    [7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
    "ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
    ERROR STACK 2
    SYSTEM ERROR: A serious error has occurred in Repository
    (c:\PROGRA~1\CSSPTEST\conplu0). Corrective action may be necessary.
    Notify
    your repository administrator.
    Class: qqsp_ImplementationException
    Error #: [1101, 198]
    Detected at: qqrp_Repository::Fetch
    Last TOOL statement: method
    SalesDevelopment_NWC.DEVNotifyofTabSetCurrent
    Error Time: Wed Dec 03 10:27:22
    Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
    (partitionId = 769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1,
    taskId =
    [769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1.22]) in application
    "ConPlus_GUI_cl0", pid 172 on node ISD42 in environment Edge.
    SYSTEM ERROR: Could not read record (64,74615) from repository data file.
    Header is corrupt.
    Class: qqsp_ImplementationException
    Error #: [1106, 612]
    Detected at: qqbt_BtreeAccess::FetchDataFileRecord
    Error Time: Wed Dec 03 10:27:22
    Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
    (partitionId = 769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1,
    taskId =
    [769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1.22]) in application
    "ConPlus_GUI_cl0", pid 172 on node ISD42 in environment Edge.
    Technote 11225 Don't reparent mapped Widgets between UserWindows at
    runtime
    It is sometimes tempting to unparent a widget from one UserWindow and
    reparent
    it into another at runtime. However, this can cause crashes if the widget
    (or
    its decendants) are "mapped" to data. Here's why...
    Suppose you have two UserWindows, UW1 and UW2. UW1 contains a DataField
    (DF1)
    which is mapped to a TextData. UW2 contains a RadioList (RL2) which is
    mapped to
    a scalar Integer. At compile time, every mapped attribute is internally
    assigned
    a "Map ID" (a small integer) which is used to tie the Widget to its
    corresponding attribute. These Map IDs are used by the Widget to look up a
    pointer to their data in a "Map" which is maintained by the UserWindow.
    Each
    UserWindow is assumed be to independent of the others, so there is nothing
    wrong
    with Widgets in different UserWindows being assigned the same Map IDs.
    In
    this
    case, let's assume that DF1 and RL2 both got assigned the same Map ID of
    3. No
    problem so far, since each lives in a separate UserWindow with a separate
    map.
    Now suppose at runtime the application "detaches" or unparents DF1 from
    its
    UserWindow and reparents it somewhere into UW2. When it comes time for DF1
    to
    paint itself the Display System it must ask the Runtime System for the
    value of
    DF1's mapped attribute. To do that it says "give me the value of the
    TextData
    for DF1. You'll find it in the Map for this UserWindow (UW1), and its Map
    ID is
    3". When the runtime system goes to do this it expects to find a TextData
    in
    this "slot" of the map, but instead it picks up the integer which is
    mapped to
    RL2. At best this leads to bad data being returned; more likely you get a
    segfault and a crash.
    If DF1 was not a mapped attribute (say, a Rectangle) there would be no
    problem
    because there is no data mapped to a Rectangle. If instead of moving DF1
    you
    created a brand new DataField on the fly there would be no problem,
    because the
    dynamic DataField would not have any Map ID and so couldn't conflict with
    any
    IDs in UW2.
    So how do you solve this problem? This is exactly what Nested Windows are
    all
    about. While you can't move DF1 into the middle of UW2, you can nest
    UW1.
    This
    works because UW1 brings its map with it, and when you access DF1 it knows
    to
    look up its value in UW1's map.
    UserWindows are intended to be the "unit of compilabilty" that can be
    nested
    inside other UserWindows. It is dangerous to "transplant" anything from
    inside
    one UserWindow into another at runtime.
    (Note that you can't avoid this problem by cloning DF1 because the MapID
    gets
    copied along with it, and the clone will fail in the same way.)
    Further details explained in related technote 12448 'Sudden client
    partition
    crashes at runtime.'
    Technote 12448 Sudden client partition crashes at runtime
    Scenario : You have two UserWindows, A and B. When Window A starts up, it
    instantiates an instance of B and reparents some component of B into A's
    window
    hierarchy.
    This is not allowed and almost always leads to an error at best or at
    worse a
    segmentation fault.
    Here's why :
    When you compile a UserWindow in Forte, each "mapped attribute" (whether a
    form
    element or menu element) is assigned an internal ID which represents an
    offset into
    that UserWindow's table of mapped attributes. This offset is only valid
    in the
    context of the UserWindow in which it was compiled. If you detach a
    FieldWidget or
    MenuWidget from one compiled Window ("tmpMenu" for example) and then
    parent
    into another compiled window ("tmpWindow") the internal ID comes with it.
    When Forte tries to make use of that copied widget it uses the ID as an
    offset
    into tmpWindow's table of mapped attributes. But that copied offset is
    meaningless in the context of tmpWindow's table, so you get some kind off
    error.
    In this case it found that the data type of the variable in the slot
    wasn't
    what
    was expected. But you might even index off the end of the table and get a
    segmentation fault.
    There is nothing to prevent you from dynamically creating menu items and
    adding
    them to a window at runtime; that will work fine. Although of course you
    can't
    access them via mapped attributes, since those can only be created at
    compile time.
    But you are not allowed to reparent a widget from one compiled UserWindow
    into
    the hierarchy of another.
    More information may be found in technote 11225 'Don't reparent mapped
    Widgets
    between UserWindows at runtime'.
    Possible errorstacks seen at runtime instead of a complete crash or
    segmentation
    violation while you are illegally reparenting a widget or menuitem between
    windows
    at runtime:
    Map::SetSubjectData: Invalid conversion from map type 0 to subject type 22
    SYSTEM ERROR: Bad parameter at location 3 in method
    qqrt_MapClassAccess::ProcessSubjectData.
    Class: qqsp_Exception
    Error #: [1001, 381]
    Detected at: qqrt_MapClassAccess::ProcessSubjectData at 3
    Error Time: Wed Aug 09 13:03:57
    Exception occurred (locally) on partition "testproject_CL0_Client",
    (partitionId = D4914A10-36C1-11D4-91B3-419AA33BAA77:0x208:0xd,
    taskId =
    [D4914A10-36C1-11D4-91B3-419AA33BAA77:0x208:0xd.68]) in application
    "FTLaunch_cl0", pid 672 on node ONEWAY in environment Audi3M2Env.
    At 13:14 26.09.00 -0400, Adamek, Zenon wrote:
    Hi,
    It is the unfixed defect 53398. Please contact Forte support.
    Zenon
    -----Original Message-----
    From: Brenda Cumming [SMTP:brenda_cummingtranscanada.com]
    Sent: Tuesday, September 26, 2000 1:15 PM
    To: Forte User group
    Subject: (forte-users) 3J=>3M new to me error
    Hi,
    We are in the process of going from 3J1 to 3.0.M.2, and I am getting
    this error that I am unfamiliar with on a GUI that works fine in 3J.
    It
    does not happen all the time, and I have been unable to establish the
    pattern that kicks it off. Has anyone seen this before?
    PS- this error is not occurring in the deployed (non-compiled) app,but
    when I am running locally from my workspace.
    SYSTEM ERROR: Bad parameter at location 6 in method
    qqrt_MapClassAccess::ProcessSubjectData.
    Class: qqsp_Exception
    Error #: [1001, 381]
    Detected at: qqrt_MapClassAccess::ProcessSubjectData at 6
    Error Time: Wed Sep 20 14:32:54
    Exception occurred (locally) on partition
    "ABSDevtStartUp_CL0_Client",
    (partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2,
    taskId =
    [36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
    application
    "Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
    SYSTEM ERROR: Can't find scope 20070 for a class.
    Class: qqsp_Exception
    Error #: [201, 11]
    Detected at: qqlo_ClassTableLoadScope at 1
    Error Time: Wed Sep 20 14:32:54
    Exception occurred (locally) on partition"ABSDevtStartUp_CL0_Client",
    (partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
    [36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
    application
    "Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
    SYSTEM ERROR: Because of a prior error, your workspace was set to
    read-only to prevent the application from attempting to write to the repository.
    The repository and work you have saved to the repository are safe. If
    your
    workspace contains unsaved work, you may use the following procedure
    to save this work. First, export the changed components. Then, shut down and
    restart this application and reopen this workspace in read-write mode.
    Finally, import the changed components and save your workspace.
    Class: qqrp_RepResourceException
    Error #: [1101, 695]
    Detected at: qqrp_Session::IsDistributed
    Last TOOL statement: method PPMeasWin.
    Error Time: Wed Sep 20 14:32:54
    Exception occurred (locally) on partition
    "ABSDevtStartUp_CL0_Client",
    (partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
    [36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
    application
    "Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
    SYSTEM ERROR: Internal Error attempting to deserialize element
    (64,120684) (fetch bitmask is 0x20). Your workspace is now read-onlyto
    prevent
    the application from attempting to write to the repository. The
    repository
    and work you have saved to the repository are safe. If your workspace
    contains unsaved work, you may use the following procedure to savethis
    work.
    First, export the changed components. Then, shut down and restart this
    application and reopen this workspace in read-write mode. Finally, import the
    changed components and save your workspace.
    Class: qqrp_RepResourceException
    Error #: [1101, 61]
    Detected at: qqrp_LogicalSession::MaterializeObject
    Error Time: Wed Sep 20 14:32:54
    Exception occurred (locally) on partition
    "ABSDevtStartUp_CL0_Client",
    (partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
    [36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
    application
    "Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
    SYSTEM ERROR: Recursive Deserialization attempted, Internal Error!
    Class: qqsp_UsageException with ReasonCode: SP_ER_INVALIDSTATE
    Error #: [301, 231]
    Detected at: qqsp_DeSerializeDriver::Run at 1
    Error Time: Wed Sep 20 14:32:54
    Exception occurred (locally) on partition"ABSDevtStartUp_CL0_Client",
    (partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
    [36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
    application
    "Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in anew
    email the word: 'Unsubscribe' to:forte-users-requestlists.xpedior.com
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

    Hi Thomas,
    Thanks for your email but I think it will be interesting for Brenda not me.
    It is exactly what I have expected from Forte Support: detailed information
    about bugs and workarounds. But what I cannot understand is that #53398 was
    released without any information about possible reasons for this problem or
    suggested workarounds. My first reaction after reading this bugreport was to
    open a new case at CallCenter to get more information about it. Please
    release more information with your bug reports !
    Regards
    Zenon Adamek
    Information Services
    Senior Programmer Analyst
    Tel: 905 712-1084 ext. 3628
    Fax: 905 712-6709
    E-mail: zadamekpurolator.com
    -----Original Message-----
    From: Thomas Degen - Sun Germany Forte Tools - Bonn
    [SMTP:thomas.degensun.com]
    Sent: Wednesday, September 27, 2000 9:49 AM
    To: Adamek, Zenon
    Cc: 'Brenda Cumming'; Forte-userslists.xpedior.com
    Subject: RE: (forte-users) 3J=>3M new to me error
    Hi Zenon,
    bug #53398 is not a bug which will likely get fixed, it's an informational
    bugreport.
    You might see an errorstack like Brenda has reported (and described in
    informational
    bugreport #53398) probably when you are doing something illegal that is
    possible
    via Forte Tool but Forte is not trapping it for performance reasons. Hence
    you will see
    the error coming from your illegal operation only at runtime, probably
    only
    while
    running interpreted in the Forte IDE, but in worst case it might be even a
    segmentation
    violation.
    Technotes 12448 'Sudden client partition crashes at runtime' and 11225
    'Don't reparent
    mapped Widgets between UserWindows at runtime' explain this matter . See
    attached.
    But maybe Brenda is much more experiencing a problem as described by Forte
    Technote 11398 'Read Only Workspace Errors using ListViews or ActiveX
    control'
    that might get easily resolved via setting of FORTE_YIELD_THROTTLE=0.
    Good Luck and Best Regards !
    BTW: I've logged bug #53398, so I've felt responsible to explain its real
    background.
    Thomas
    Thomas Degen
    Sun Microsystems - Forte Tools
    Forte CTE & Sustaining Group
    Technical Support Germany
    tel.:+49.228/91499-50
    MailTo:thomas.degensun.com
    Technote 11398 Read Only Workspace Errors using ListViews or ActiveX
    control
    SCENARIO:
    Getting some unusual interpreter errors that result in an error stating
    that
    the workspace has been set to read only. Please see Enclosures for the
    two
    most common error stacks that have been encountered. The abbreviated
    versions of the errors are:
    - Can't read record (record size = -1)
    - Id in index does not match id in record header in data file
    - Recursive deserialization attempted.
    - Unknown Mark type in deserialization
    - Could not read record (64,74615) from repository data file.
    Header
    is corrupt.
    These errors can be happening in either the development environment when
    running from one of the development workshops, or with the deployed
    application.
    The bug outlined in this Technote may be the culprit if the errors above
    are
    seen when running a client on Windows NT or Motif and the user interface
    incorporates ActiveX controls or ListView/TreeView widgets.
    CAUSE:
    Basically what is happening is that in rare circumstances Forte may invoke
    a
    nested copy of the interpreter while the first interpreter has yielded.
    This
    is not a problem in and of itself, but in the case where the original
    interpreter was in the middle of a repository fetch when it yielded, and
    the second interpreter needs to fetch code as well, we will get one of the
    errors listed above, depending on the exact timing. The reason for the
    errors is that the repository code at this level is thread-safe but not
    re-entrant. It is protected by a mutex that is already owned by the
    current task. Which, given the scenario outlined here, where the two
    interpreters are running inside of the same task, results in the nested
    interpreter being allowed to change data out from under the first.
    While for every fetch one or more calls to WindowSystem.Yield will be made
    (this is there to prevent the semblance of system lock-up on Win 3.1,
    where
    Yield is the only way other applications can be allowed to run), there is
    a parameter which controls how often to actually yield, which by default
    is
    set to one out of every 100 calls. This is the reason the problem is
    intermittent--you need a yield to occur during a repository fetch
    which starts another interpreter which also needs to fetch code from
    disk.
    The reason this has only surfaced recently is that the nested interpreter
    scenario can only happen in 2 cases that we know of:
    - ActiveX controls which respond to events/Windows messages
    - Outline fields/ListViews with column(s) mapped to virtual
    attributes
    In all other normal cases, the yield can process the message (typically a
    paint message) without starting another interpreter, so regardless of
    whether
    the first interpreter yielded during a repository operation or not, there
    is
    no conflict.
    SOLUTION:
    The workaround is to prevent yields altogether by setting the
    FORTE_YIELD_THROTTLE environment variable equal to 0 in the client's
    environment. This should have no detrimental effects since the yield code
    is in place solely for Windows 3.1x clients.
    ERROR STACK 1
    SYSTEM ERROR: Because of a prior error, your workspace was set to
    read-only to
    prevent the application from attempting to write to the repository. The
    repository and work you have saved to the repository are safe. If your
    workspace
    contains unsaved work, you may use the following procedure to save this
    work.
    First, export the changed components. Then, shut down and restart this
    application and reopen this workspace in read-write mode. Finally, import
    the
    changed components and save your workspace.
    Class: qqrp_RepResourceException
    Error #: [1101, 695]
    Detected at: qqrp_Session::GetObjectById
    Last TOOL statement: method EFWindowController.EFEventLoop
    Error Time: Tue Nov 18 15:58:47
    Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
    (partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
    taskId =
    [7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
    "ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
    The remainder of the Error Manager stack is:
    SYSTEM ERROR: Internal Error attempting to deserialize element (64,67470)
    (fetch
    bitmask is 0x20). Your workspace is now read-only to prevent the
    application
    from attempting to write to the repository. The repository and work you
    have
    saved to the repository are safe. If your workspace contains unsaved work,
    you
    may use the following procedure to save this work. First, export the
    changed
    components. Then, shut down and restart this application and reopen this
    workspace in read-write mode. Finally, import the changed components and
    save
    your workspace.
    Class: qqrp_RepResourceException
    Error #: [1101, 61]
    Detected at: qqrp_LogicalSession::MaterializeObject
    Last TOOL statement: method EFTabManagerNew.EFNoteBookHandler
    Error Time: Tue Nov 18 15:58:47
    Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
    (partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
    taskId =
    [7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
    "ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
    SYSTEM ERROR: Unknown Mark type in deserialization.
    Class: qqsp_ImplementationException
    Error #: [1101, 34]
    Detected at: qqrp_DeSerializeObject::ProcessHdr
    Error Time: Tue Nov 18 15:58:47
    Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
    (partitionId = 7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1,
    taskId =
    [7EFAE060-4AFA-11D1-A1C1-1FDC8A99AA77:0x446:0x1.23]) in application
    "ConPlus_GUI_cl0", pid 147 on node ISD060 in environment EdgeTest.
    ERROR STACK 2
    SYSTEM ERROR: A serious error has occurred in Repository
    (c:\PROGRA~1\CSSPTEST\conplu0). Corrective action may be necessary.
    Notify
    your repository administrator.
    Class: qqsp_ImplementationException
    Error #: [1101, 198]
    Detected at: qqrp_Repository::Fetch
    Last TOOL statement: method
    SalesDevelopment_NWC.DEVNotifyofTabSetCurrent
    Error Time: Wed Dec 03 10:27:22
    Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
    (partitionId = 769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1,
    taskId =
    [769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1.22]) in application
    "ConPlus_GUI_cl0", pid 172 on node ISD42 in environment Edge.
    SYSTEM ERROR: Could not read record (64,74615) from repository data file.
    Header is corrupt.
    Class: qqsp_ImplementationException
    Error #: [1106, 612]
    Detected at: qqbt_BtreeAccess::FetchDataFileRecord
    Error Time: Wed Dec 03 10:27:22
    Exception occurred (locally) on partition "ConPlus_GUI_cl0_Client",
    (partitionId = 769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1,
    taskId =
    [769D4310-6B88-11D1-84FD-65BF87C8AA77:0x121:0x1.22]) in application
    "ConPlus_GUI_cl0", pid 172 on node ISD42 in environment Edge.
    Technote 11225 Don't reparent mapped Widgets between UserWindows at
    runtime
    It is sometimes tempting to unparent a widget from one UserWindow and
    reparent
    it into another at runtime. However, this can cause crashes if the widget
    (or
    its decendants) are "mapped" to data. Here's why...
    Suppose you have two UserWindows, UW1 and UW2. UW1 contains a DataField
    (DF1)
    which is mapped to a TextData. UW2 contains a RadioList (RL2) which is
    mapped to
    a scalar Integer. At compile time, every mapped attribute is internally
    assigned
    a "Map ID" (a small integer) which is used to tie the Widget to its
    corresponding attribute. These Map IDs are used by the Widget to look up a
    pointer to their data in a "Map" which is maintained by the UserWindow.
    Each
    UserWindow is assumed be to independent of the others, so there is nothing
    wrong
    with Widgets in different UserWindows being assigned the same Map IDs.
    In
    this
    case, let's assume that DF1 and RL2 both got assigned the same Map ID of
    3. No
    problem so far, since each lives in a separate UserWindow with a separate
    map.
    Now suppose at runtime the application "detaches" or unparents DF1 from
    its
    UserWindow and reparents it somewhere into UW2. When it comes time for DF1
    to
    paint itself the Display System it must ask the Runtime System for the
    value of
    DF1's mapped attribute. To do that it says "give me the value of the
    TextData
    for DF1. You'll find it in the Map for this UserWindow (UW1), and its Map
    ID is
    3". When the runtime system goes to do this it expects to find a TextData
    in
    this "slot" of the map, but instead it picks up the integer which is
    mapped to
    RL2. At best this leads to bad data being returned; more likely you get a
    segfault and a crash.
    If DF1 was not a mapped attribute (say, a Rectangle) there would be no
    problem
    because there is no data mapped to a Rectangle. If instead of moving DF1
    you
    created a brand new DataField on the fly there would be no problem,
    because the
    dynamic DataField would not have any Map ID and so couldn't conflict with
    any
    IDs in UW2.
    So how do you solve this problem? This is exactly what Nested Windows are
    all
    about. While you can't move DF1 into the middle of UW2, you can nest
    UW1.
    This
    works because UW1 brings its map with it, and when you access DF1 it knows
    to
    look up its value in UW1's map.
    UserWindows are intended to be the "unit of compilabilty" that can be
    nested
    inside other UserWindows. It is dangerous to "transplant" anything from
    inside
    one UserWindow into another at runtime.
    (Note that you can't avoid this problem by cloning DF1 because the MapID
    gets
    copied along with it, and the clone will fail in the same way.)
    Further details explained in related technote 12448 'Sudden client
    partition
    crashes at runtime.'
    Technote 12448 Sudden client partition crashes at runtime
    Scenario : You have two UserWindows, A and B. When Window A starts up, it
    instantiates an instance of B and reparents some component of B into A's
    window
    hierarchy.
    This is not allowed and almost always leads to an error at best or at
    worse a
    segmentation fault.
    Here's why :
    When you compile a UserWindow in Forte, each "mapped attribute" (whether a
    form
    element or menu element) is assigned an internal ID which represents an
    offset into
    that UserWindow's table of mapped attributes. This offset is only valid
    in the
    context of the UserWindow in which it was compiled. If you detach a
    FieldWidget or
    MenuWidget from one compiled Window ("tmpMenu" for example) and then
    parent
    into another compiled window ("tmpWindow") the internal ID comes with it.
    When Forte tries to make use of that copied widget it uses the ID as an
    offset
    into tmpWindow's table of mapped attributes. But that copied offset is
    meaningless in the context of tmpWindow's table, so you get some kind off
    error.
    In this case it found that the data type of the variable in the slot
    wasn't
    what
    was expected. But you might even index off the end of the table and get a
    segmentation fault.
    There is nothing to prevent you from dynamically creating menu items and
    adding
    them to a window at runtime; that will work fine. Although of course you
    can't
    access them via mapped attributes, since those can only be created at
    compile time.
    But you are not allowed to reparent a widget from one compiled UserWindow
    into
    the hierarchy of another.
    More information may be found in technote 11225 'Don't reparent mapped
    Widgets
    between UserWindows at runtime'.
    Possible errorstacks seen at runtime instead of a complete crash or
    segmentation
    violation while you are illegally reparenting a widget or menuitem between
    windows
    at runtime:
    Map::SetSubjectData: Invalid conversion from map type 0 to subject type 22
    SYSTEM ERROR: Bad parameter at location 3 in method
    qqrt_MapClassAccess::ProcessSubjectData.
    Class: qqsp_Exception
    Error #: [1001, 381]
    Detected at: qqrt_MapClassAccess::ProcessSubjectData at 3
    Error Time: Wed Aug 09 13:03:57
    Exception occurred (locally) on partition "testproject_CL0_Client",
    (partitionId = D4914A10-36C1-11D4-91B3-419AA33BAA77:0x208:0xd,
    taskId =
    [D4914A10-36C1-11D4-91B3-419AA33BAA77:0x208:0xd.68]) in application
    "FTLaunch_cl0", pid 672 on node ONEWAY in environment Audi3M2Env.
    At 13:14 26.09.00 -0400, Adamek, Zenon wrote:
    Hi,
    It is the unfixed defect 53398. Please contact Forte support.
    Zenon
    -----Original Message-----
    From: Brenda Cumming [SMTP:brenda_cummingtranscanada.com]
    Sent: Tuesday, September 26, 2000 1:15 PM
    To: Forte User group
    Subject: (forte-users) 3J=>3M new to me error
    Hi,
    We are in the process of going from 3J1 to 3.0.M.2, and I am getting
    this error that I am unfamiliar with on a GUI that works fine in 3J.
    It
    does not happen all the time, and I have been unable to establish the
    pattern that kicks it off. Has anyone seen this before?
    PS- this error is not occurring in the deployed (non-compiled) app,but
    when I am running locally from my workspace.
    SYSTEM ERROR: Bad parameter at location 6 in method
    qqrt_MapClassAccess::ProcessSubjectData.
    Class: qqsp_Exception
    Error #: [1001, 381]
    Detected at: qqrt_MapClassAccess::ProcessSubjectData at 6
    Error Time: Wed Sep 20 14:32:54
    Exception occurred (locally) on partition
    "ABSDevtStartUp_CL0_Client",
    (partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2,
    taskId =
    [36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
    application
    "Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
    SYSTEM ERROR: Can't find scope 20070 for a class.
    Class: qqsp_Exception
    Error #: [201, 11]
    Detected at: qqlo_ClassTableLoadScope at 1
    Error Time: Wed Sep 20 14:32:54
    Exception occurred (locally) on partition"ABSDevtStartUp_CL0_Client",
    (partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
    [36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
    application
    "Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
    SYSTEM ERROR: Because of a prior error, your workspace was set to
    read-only to prevent the application from attempting to write to the repository.
    The repository and work you have saved to the repository are safe. If
    your
    workspace contains unsaved work, you may use the following procedure
    to save this work. First, export the changed components. Then, shut down and
    restart this application and reopen this workspace in read-write mode.
    Finally, import the changed components and save your workspace.
    Class: qqrp_RepResourceException
    Error #: [1101, 695]
    Detected at: qqrp_Session::IsDistributed
    Last TOOL statement: method PPMeasWin.
    Error Time: Wed Sep 20 14:32:54
    Exception occurred (locally) on partition
    "ABSDevtStartUp_CL0_Client",
    (partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
    [36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
    application
    "Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
    SYSTEM ERROR: Internal Error attempting to deserialize element
    (64,120684) (fetch bitmask is 0x20). Your workspace is now read-onlyto
    prevent
    the application from attempting to write to the repository. The
    repository
    and work you have saved to the repository are safe. If your workspace
    contains unsaved work, you may use the following procedure to savethis
    work.
    First, export the changed components. Then, shut down and restart this
    application and reopen this workspace in read-write mode. Finally, import the
    changed components and save your workspace.
    Class: qqrp_RepResourceException
    Error #: [1101, 61]
    Detected at: qqrp_LogicalSession::MaterializeObject
    Error Time: Wed Sep 20 14:32:54
    Exception occurred (locally) on partition
    "ABSDevtStartUp_CL0_Client",
    (partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
    [36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
    application
    "Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
    SYSTEM ERROR: Recursive Deserialization attempted, Internal Error!
    Class: qqsp_UsageException with ReasonCode: SP_ER_INVALIDSTATE
    Error #: [301, 231]
    Detected at: qqsp_DeSerializeDriver::Run at 1
    Error Time: Wed Sep 20 14:32:54
    Exception occurred (locally) on partition"ABSDevtStartUp_CL0_Client",
    (partitionId = 36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2, taskId =
    [36172000-5DA8-11D4-B1F0-14015EDAAA77:0x2da:0x2.25]) in
    application
    "Forte_cl0", pid 93 on node T5621 in environment AbisDMEnv.
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in anew
    email the word: 'Unsubscribe' to:forte-users-requestlists.xpedior.com
    For the archives, go to: http://lists.xpedior.com/forte-users and use
    the login: forte and the password: archive. To unsubscribe, send in a new
    email the word: 'Unsubscribe' to: forte-users-requestlists.xpedior.com

  • Auto logins on websites no longer working

    I recently (a couple days ago) got a pop-up on the lower part of my screen that said that firefox was going kind of slowly or something along those lines and said if I would like to fix this that I could click this button. Well I did that and it took me to a page that talked about resetting firefox to its default settings but that all info pretty much would be kept correct like my passwords, bookmarks, addons, and other things like that. Well I said what the heck and tried it and when it was finally done doing what ever it was doing I get back online with none of my opening tabs aloud to be there so that was wiped out, my book marks were there so that was good, but all of my addons like X-notifier and things like that were now gone, and when I go to pages now it has no idea who I am. My user names don't show up or the passwords. I can login to them and it might be fine for 5-10 minutes but then all of a sudden it tells me that I need to login all over again. Even my X-notifier does it and its supposed to know my login permanently so I never have to type it in. But I can be in the middle of sorting my emails and trying to delete something get a message that says I am no longer signed in to my email account.
    I have searched all over in the tools>options area and made sure everything is the same as it used to be with saving passwords and even scrolled through my stuff saved to see if something had gotten deleted but they are all there and I see no reason why it would not log me in to the ANY site. I know some of the sites out there don't like to allow auto login stuff which I am fine with but some of these websites I am the owner of and I know for a fact that its not my site doing it. The repeated login issue is really getting on my nerves cause its started to disturb my daily working. Please help me with figuring this out.
    Thanks
    Troy

    I am going to try the stuff mentioned by you above and see if it helps. I know its affecting this site as well and isn't keeping logged in at all as I have had to re-type my password each time I come here.

Maybe you are looking for