Multiple Plugin HTTP Sessions

Hello everybody
We have developed a BSP that is displayed in a Portals using an iView. When the user navigate to this iView a Plugin HTTP Session appears in the R/3 system.
If the user navigate to another iView and after a while he/she returns to the BSP iView, a new Plugin HTTP Session apears in the R/3 system.
Is possible to avoid this? Can a user have a unique session?
Thank you in advanced.
Rubé

As much I understand this.
This is the default feature of BSP .You are using an I View ,you have plugin http session  and one RFC connection in R3.
Now once you leave leave the BSP page ,Your plug in session shall be finished since it is no more using that BSP.
Once you come back to the same page ,I believe you get the new session for that BSP.
In my point of view ,My reply is No but you can check with developers if they can modify sessions mechanism ?
Thanks
Hope this helps you.
Amit

Similar Messages

  • Bw web report plugin http session hangs at the server side

    Hi,
    I am having problems when closing the browser of a BW web report. After I closed the browser by going File->close, I ran SM04 and found out the Plugin HTTP session hangs at the server side.
    How can we terminate the Plugin HTTP session at the server side when user closes the internet browser?
    I did implement a logoff function at my web template, if user clicks on the logoff, the Plugin HTTP session is terminated at server side correctly. But As you know, 50% of time user will close the report by closing the internet browser instead of clicking the logoff. That leaves lots of hanging Plugin HTTP sessions at our server side.
    By the way, we actived our BEX service at the SICF.
    Thanks for help!
    JA

    Hi
    If you want to avoid a blank page with logoff button, add opener=0
    <a href="<SAP_BW_URL CMD='LOG_OFF' ~command='logoff'
    >" onClick="javascript:window.close(opener=0);">Log off</a>
    If you want to close the session via X, use this code:
    create a sapscript function
    function closeSession()
    logoff()
    window.unload=CloseSession()
    However, the Plugin HTTP session isn't killed.
    Regards

  • Using Voice Browsers, creates multiple HTTP Sessions

    I am using the default voicebrowser.aef script.
    I do a Create URL Document step followed by a Voice Browser step.
    The VXML developer is telling me the different HTTP sessions are getting created for the 2 steps and it is extremely critical that the same HTTP session is used throughtout the call.
    Does anyone have any insight on this or know of a way I set it to use the same session thourghout?
    Ive attached screen shots of my script...
    This is the log excerpt from the VXML log...
    DEBUG [2011-04-21 08:57:16,950] [http-8080-1] [CallController] [] - : ~~~HTTPSession ID: 86DD667F1ED8C42D8430D4DE8D38ED9A
    DEBUG [2011-04-21 08:57:16,952] [http-8080-1] [CallController] [] - : ~~~HTTPSession Creation Time: 1303394236902
    DEBUG [2011-04-21 08:57:16,952] [http-8080-1] [CallController] [] - : ~~~HTTPSession Last Accessed: 1303394236902
    DEBUG [2011-04-21 08:57:16,953] [http-8080-1] [CallController] [] - : ****** PARAMETERS :  *********
    DEBUG [2011-04-21 08:57:16,953] [http-8080-1] [CallController] [] - :       txtDNIS = 7079
    DEBUG [2011-04-21 08:57:16,953] [http-8080-1] [CallController] [] - :       txtANI = 6516864319
    DEBUG [2011-04-21 08:57:16,955] [http-8080-1] [CallController] [] - :       UserInput =
    DEBUG [2011-04-21 08:57:16,955] [http-8080-1] [CallController] [] - :       FromState = 0
    DEBUG [2011-04-21 08:57:16,955] [http-8080-1] [CallController] [] - :       txtCTIID = 1234567890
    DEBUG [2011-04-21 08:57:16,955] [http-8080-1] [CallController] [] - :       txtLineNbr = 1
    DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - : ~~~HTTPSession ID: B64DDD4D99F4A4A490B35DC5BA817928
    DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - : ~~~HTTPSession Creation Time: 1303394238044
    DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - : ~~~HTTPSession Last Accessed: 1303394238044
    DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - : ****** PARAMETERS :  *********
    DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - :       TimeOutCount = 0
    DEBUG [2011-04-21 08:57:18,044] [http-8080-2] [CallController] [] - :       FromState = 1
    DEBUG [2011-04-21 08:57:18,045] [http-8080-2] [CallController] [] - :       BadCount = 0

    As much I understand this.
    This is the default feature of BSP .You are using an I View ,you have plugin http session  and one RFC connection in R3.
    Now once you leave leave the BSP page ,Your plug in session shall be finished since it is no more using that BSP.
    Once you come back to the same page ,I believe you get the new session for that BSP.
    In my point of view ,My reply is No but you can check with developers if they can modify sessions mechanism ?
    Thanks
    Hope this helps you.
    Amit

  • Webdynpro ABAP/Portal. Plugin HTTP connection issue on WaitingEventQueue.js

    Hello,
    We are experiencing a strange Portal Behavior with our Webdynpros. Our portal contains several iViews including some Webdynpro (ABAP) and some reporting transaction calls that use SAPgui for HTML.
    When portal is called for the first time and a user logs in, two connections of type RFC can be seen for that user in SM04 in our ERP system. All iViews work as expected. For example, calling the Time Management webdynpro closes one of the RFC connections and starts a new Pluguin HTTP connection. We can go back and forth between the welcome page and this Webdynpro with no issues.
    If we then select one of the reporting transaction codes, the portal launches the SAPGUI for HTML. Report retrieves and shows data, and then we close using the "Exit" button provided by the sapgui for HTML
    Next we try again to launch any webdynpro (abap), but SM04 shows that the new Plugin HTTP session gets stuck and spinning mid way, and will stay there. Refreshing the Portal screen with F8, navigating back and forth, logging off and on again has no effect. The webdynpros will not launch again. Only webdynpros are affected, any of the reporting transactions can be called successfully over and over.
    We have figured that deleting Temporary Internet files (we are using IE 7), and in particular by just deleting the WaitingEventQueue.js?XXXXXXXXXXX file, the system will break away from the spin loop and show the webdynpro again, but eventually it will get stuck again, and asking the users to delete their Temporary Internet Files every 5 minutes is not a workable solution
    I have reviewed the contents of this javascript file at different points during the test, and the contents do not change, so deleting the file and the recreate process must be resetting somehow the queue and allowing for a new correct communication.
    Is there a way to properly reset this event queue (for example from ABAP, when the webdynpros are reloaded) in order to avoid the spin loop?
    Thanks for any help!
    Andres

    Well, we got the issue resolved, so here is what we did, in case anybody is interested:
    Tested again our portal with multiple versions of Internet Explorer, in particular IE8 and IE6, the Webdynpro behavior was normal (no timeouts or locks). It even worked when we installed IE7 in a brand new machine and tried our portal.
    So we started suspecting if maybe the particular IE7 that we install internally (with specific settings and policies) may be the culprit. We took a desktop that was producing the timeouts and used the following options in IE7:
    Tools->Internet Options->Advanced(tab)-Reset Internet Explorer settings
    and, voila! the next time we ran there, the portal did not create any timeouts.
    We even asked our desktop support team to uninstall and reinstall IE7 in the same machine after we did the reset, and even after the re-install that the timeout problems did not re-appear.
    One of the things that the "reset" option does is delete the Add-ons used by IE.
    So as a last test, we took a machine that was presenting the problem and went to the Internet Options to disable all the add-ons (in the Programs Tab). The error disappeared.
    And even after enabling back all the add-ons, the error would not return.
    Conclusion:
    Without being able to pinpoint the specific add-on (or combination) that causes the problem, we suspect that some of them conflicted, causing IE7 to behave abnormally. Disabling them all, restarting Internet Explorer, and enabling them again, makes the WaitingEventQueue.js work as it should

  • How to close a HTTP session when a user closes the window

    Hi,
    I am having problems when closing the browser of a BW web report. After I closed the browser by going File->close, I ran SM04 and found out the Plugin HTTP session hangs at the server side.
    How can we terminate the Plugin HTTP session at the server side when user closes the internet browser?
    I did implement a logoff function at my web template and this was implimented on the Menu page, if user clicks on the logoff, the Plugin HTTP session is terminated at server side correctly.
    If user navigates to the other pages from the main page... then the logoff function was not implimented in the other pages. So many of the users are closing the windows directly. Eevn if we impliment logoff in all the subpages, As you know, 50% of time user will close the report by closing the internet browser instead of clicking the logoff. That leaves lots of hanging Plugin HTTP sessions at our server side.
    Regards,
    Tony

    Hi,
    And also take a look on the Genral property of the web template. We solved this problem by changing only this property (no extra things).
    <b>Property:                            Value</b>
    Automatic Session Management:           Active
    With rgds,
    Anil Kumar Sharma .P
    Message was edited by: Anil Kumar Sharma

  • Sun One (Netscape) Plugin: Losing HTTP Session Problem

    Hi All,
    We are having some trouble with HTTP sessions. Sometimes our browser will have a session cookie set but will be issued a new session cookie anyways. This seems to occur only one in every 10 attempts, and seems to occur more frequently on certain machines. When this occurs we lose all of the session data that we were previously using.
    Our environment is as follows:
    We have three load balanced Sun One Web Servers fronting 6 mananged 8.1 sp5 web logic instances. We've verified that multicast is working and that we've configured the plugin/application to have a unique cookie name already. We've also set the persistence type to 'replicated'
    Only clue that we have so far comes from our plug-in logs. It seems to be complaining about connection pooling:
    Mon Jan 22 16:04:39 2007 getPooledConn: No more connections in the pool for Host[XXX.XXX.XXX.XXX] Port[8003] SecurePort[8004]
    Mon Jan 22 16:04:39 2007 Connect returns -1, and error no set to 55, msg 'A connect operation on a socket is not complete.'
    Any ideas? Thanks in advance!
    Regards,
    Ray Siu

    Check if your web app has the same cookie name (weblogic.xml) as defined in the obj.conf.
    Jin

  • Sharing HTTP session on multiple logins

    If two users login into an application with same credentials and from different browsers can i use same http session to handle both the clients.
    My objective is how many ever users login with same credentials we use same session to handle them.
    I do not want to stop multiple login with same credentials.

    Associate the data with the logged in user instead of the session then.

  • Share http session across multiple EARs

    I am curious to know the following:-
    --> is it possible to share http session across multiple EARs running on same Weblogic application server.
    i.e weblogic server/Jboss
    --> is it possible to share http session across multiple EARs running on different Weblogic application server.
    i.e weblogic server/Jboss
    Please share the steps/way to acheive the same.

    What are you trying to achieve / accomplish by splitting it up?
    e.g. Clean Build in workshop will be faster for multiple EAR's , but unless you have all your application level libraries as shared libraries you might increase your runtime footprint. or you might want independent deploy/redeploy for your apps etc.
    If however you need the session to be shared , that these aren't really independent web-applications and shouldn't be separate ear's. In most cases though you dont actually need the session as shared (e.g. a user's data is fetched from the database , you dont really need the session shared, you need a single shared sign on). So when you say is the session shared, what is the data that you need shared? should it be in the session in the first place?
    And finally are these webapp's really independent (functionally ) or not?
    Edited by: deepshet on Oct 13, 2009 2:09 PM

  • In-memory replication of http session is not working in BEA7 cluster

              Hi everyone,
              I have 3 managed servers in Bea7.0 SP4 in a cluster. The client requests are sent
              through apache web server. I have given cluster address as URL in httpd.conf of
              apache server which sends the client requests for dynamic pages such as JSPs and
              servlets to the weblogic cluster.
              Load balancing is working fine. I ensured this from the log files of all the 3
              servers. All the 3 servers are getting different client requests and thus load
              balancing is working.
              Now, I wanted to achieve Fail-over. I do not think that i should use proxy plug-in
              for this. I feel the cluster itself will handle fail-over provided i make the
              http session as memory replicated.
              I updated the weblogic.xml with the following entry :
              <session-descriptor>
              <param-name>PersistentStoreType</param-name>
              <param-value>replicated</param-value>
              </session-param>
              </session-descriptor>
              I guess this is sufficient to make the http session as cluster aware.
              But when I shutdown server1, the user connected to server1 will be kicked out
              of the session and come to login page through server2 or server3 which are running
              fine.
              Could anyone help me to achieve http session as cluster aware. Does it indicate
              that I have to go for WLS proxy – HttpClusterServlet to achieve fail over for
              http session ?
              BTW, for your info, i am using setAttribute() and getAttribute() while manipulating
              the session.
              thanks in advance.
              

              Hi Ryan,
              Thanks for ur valuable input.
              I can see failover working.
              But, I can not continue with the same session in my application.
              I printed session Ids before and after failover, I found both are different.
              I guess session replication is a responsibility of weblogic/apache plugin.
              If not please let me know which all settings I should do to make failover working?
              Thanks again.
              Plad
              "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
              >Plad,
              >
              >Are you trying to gracefully shut down the server? If you are then the
              >problem that you say you can't identify is simply the server's default
              >behavior which is to wait for all non-replicated sessions to be dropped
              >or
              >timed out before killing the process. Try forcing the shutdown: kill
              >-9 the
              >PID or CTRL-C if you started the server from the command line. You can
              >also
              >check the ``Ignore Sessions During Shutdown" checkbox under the server's
              >control tab in the admin console, this should allow you to shut down
              >gracefully without waiting for session timeout. BTW your sequence is
              >off
              >in #5 below, the replication doesn't occur upon failure, the replication
              >has
              >already happened once you created the session object on the first server,
              >I
              >think maybe you're confusing replication with failover.
              >
              >~RU
              >
              >"Plad" <[email protected]> wrote in message
              >news:[email protected]...
              >>
              >> Hi,
              >> I have 2 managed servers in a cluster.
              >>
              >> 1. I have got a DNS name configured which maps to these 2 managed server's
              >IP
              >> addresses.
              >> 2. I can browse my site using this DNS name.
              >> In HTTPD.conf I have :
              >>
              >> ServerName dev.a.b.net
              >>
              >> <IfModule mod_weblogic.c>
              >> WebLogicCluster 10.1.38.232:7023,10.1.34.51:7023
              >> MatchExpression *.*
              >> </IfModule>
              >>
              >> LoadModule weblogic_module modules/mod_wl_20.so
              >>
              >> 3. I have adeded session descriptor in weblogic.xml , also enabled
              >proxy
              >plugin
              >> in weblogic console.
              >>
              >> 4. I tested accessing my application using DNS url after shutting down
              >alternatively
              >> each manaed server. I can access application.
              >>
              >> 5. Now, problem comes when I access a managed server1 , keeping server2
              >down.
              >> I am able to access my application.
              >> Now, I start the server2.
              >> (Here I am supposing that replication should occur)
              >> Then I am shutting down server1.
              >> But, this time the server log shows me following:
              >>
              >>
              >> 9:58:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
              >non-replicated
              >> sessions after 2 minutes of initiating SUSPEND. Waiting for non-replicated
              >sessions
              >> to finish.
              >> 10:00:51 AM GMT+05:30 NOTICE Web application(s) chlist still have
              >non-replicated
              >> sessions after 4 minutes of initiating SUSPEND. Waiting for non-replicated
              >sessions
              >> to finish.
              >>
              >> I am unable to make out where the problem is?
              >> Can it be a problem of Liecense? Is there any specialcluster liecense
              >for
              >weblogic8?
              >>
              >> Hoping to get replies.
              >> Thanx.
              >> Plad
              >>
              >> "ryan upton" <ryanjupton at learningvoyage dot com> wrote:
              >> >See my reply to your first post, but I've also added a few comments
              >here.
              >> >
              >> >"jyothi" <[email protected]> wrote in message
              >> >news:[email protected]...
              >> >>
              >> >> I guess someone from bea support team only can answer both your
              >question
              >> >and mine.
              >> >> As per my knowledge, we do not need to do any setup at Apache
              >side
              >> >regarding
              >> >> cluster other than mentioning cluster address as URL while
              >contacting
              >> >WLS
              >> >> from apache.
              >> >>
              >> >> I hope someone from Bea, will help us. I do not think that we
              >> >go for
              >> >WLS
              >> >> proxy plug-in using HttpClusterServlet for making session replication.
              >> > I
              >> >strongly
              >> >> feel that the cluster itself be able to manage the fail-over of
              >> >http
              >> >sessions
              >> >> provided we put the entry "PersistentStoreType" in weblogic.xml
              >> >regarding
              >> >> the session replication.
              >> >>
              >> >
              >> >The cluster does handle the management of Sessions. The clustered
              >> >applications still create the Session objects and the cluster manages
              >> >them
              >> >as per your deployment descriptor settings (replicated, JDBC, File)
              >however
              >> >the proxy has to be aware of which server the client has an affinity
              >> >for
              >> >(only with replicated sessions) and it does that by reading a cookie
              >> >passed
              >> >back from the server that handled the initial request and created
              >the
              >> >primary session object. The proxy has a list of both the primary
              >and
              >> >secondary server locations from this cookie that it can use to failover
              >> >the
              >> >request if the primary server fails. Clusters _DO NOT_ failover nor
              >> >do they
              >> >load balance, that's the job of your proxy, whether you're using the
              >> >HTTPClusterServlet, WLS Plug-in or a more sophisticated hardware load
              >> >balancer like Big IPs F5
              >> >
              >> >> jyothi
              >> >>
              >> >
              >> >~RU
              >> >
              >> >
              >>
              >
              >
              

  • Losing HTTP Sessions

    Hi All,
              We are having some trouble with HTTP sessions. Sometimes our browser will have a session cookie set but will be issued a new session cookie anyways. This seems to occur only one in every 10 attempts, and seems to occur more frequently on certain machines. When this occurs we lose all of the session data that we were previously using.
              Our environment is as follows:
              We have three load balanced Sun One Web Servers fronting 6 mananged 8.1 sp5 web logic instances. We've verified that multicast is working and that we've configured the plugin/application to have a unique cookie name already. We've also set the persistence type to 'replicated'
              Only clue that we have so far comes from our plug-in logs. It seems to be complaining about connection pooling:
              Mon Jan 22 16:04:39 2007 getPooledConn: No more connections in the pool for Host[XXX.XXX.XXX.XXX] Port[8003] SecurePort[8004]
              Mon Jan 22 16:04:39 2007 Connect returns -1, and error no set to 55, msg 'A connect operation on a socket is not complete.'
              Any ideas? Thanks in advance!
              Regards,
              Ray Siu

    To the OP (jirey)
              This issue is 8 months old without a resolution posted, were you able to get past this?
              Thanks

  • How to do http session stickiness based on URL patterns?

    Is there a feature within the WL plugin for Apache that would allow me to emulate the "jvmroute" session stickiness behaviour as provided by Tomcat and its plugin. I would like to have the control to tie requests from http clients to particular WLS servers in a cluster depending on the URL. For example http://foo.com/web01 requests would be forwarded to an appsererver app01 and so on. For all other requests (e.g http://foo.com/web), the WL plugin would do its normal load balancing ignoring the stickiness. From my understanding the WLS inbuilt http session stickiness is based on JSessionIDs which are exchanged using cookies - which is something i cannot use in my case since i want the stickiness based on URL patterns.
    I am using WLS 10.0 with Apache 2.2.4 on Linux.
    Thanks
    Ramdas

    Session is not replicated across all the servers in the Cluster.
    Apache knows which server to go using the JSession ID.
    There is a concept of primary and secondary, secondary is selected based on the replication groups there are configured in the cluster.
    you can configure the cluster so that /web01 requests go to different cluster, and /web requests go to different cluster.
    but you can get all the funtiionalities from the single cluster.
    Do you have any java caching that you are not able to replicate across the cluster ?(I know this can be done too).
    let me know what you are actually trying to solve by doing the behavior you explained.

  • [svn:bz-trunk] 21394: bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX .

    Revision: 21394
    Revision: 21394
    Author:   [email protected]
    Date:     2011-06-16 12:34:13 -0700 (Thu, 16 Jun 2011)
    Log Message:
    bug fix for watson 2887837 Not getting duplicate session detected error when same flex client id is used from two different HTTP sessions in CRX.
    get the sessions id before we invalidate the duplicate session.
    Checkintests pass
    Modified Paths:
        blazeds/trunk/modules/core/src/flex/messaging/endpoints/BaseHTTPEndpoint.java

    For our profect I think this issue was caused as follows:
    Believing that remoting was full asynchronous we fired a 2 or 3 remote calls to the server at the same time ( within the same function ) - usually when the users goes to a new section of the app.
    This seemed to trigger the duplicate http session error since according to http://blogs.adobe.com/lin/2011/05/duplication-session-error.html  two remote calls arriving before a session is created will cause 2 sessions to be created.
    Our current solution ( too early to say it works ) is to daisy chain the multiple calls together .
    Also there seemed to be an issue where mobile apps that never quit ( thanks Apple! )  caused the error when activated after a few hours.
    I guess the session expires on the server and the error above occurs on activation.
    So the mobile apps now ping the server with a remote call when activated after sleeping for more than one hour.
    All duplicate http errors are silently caught and reported.
    Fingers crossed we won't get any more!

  • HTTP Session caching possible using WL7 JAX-RPC ?

    We're using WL7, and using the JAX-RPC API to access external webservices.
    Basically, we create the appropriate 'stubs' from the target WSDL using
    clientgen. Then we invoke the target method. Code looks something like this:
    Client_Impl client = new Client_Impl; // implementation of target
    ClientPort_Stub stub = client.getClientPort();
    stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, url)
    stub.invoke(args);
    Now, when is the actual endpoint URL being created ? Is it when the invoke()
    method is called ?
    It cannot be during the constructor since I pass the target URL after that ...
    My problem is that I have to call the 'invoke' method quite frequently, and hence
    would like the HTTP session to be reused, rather than recreated each time. Right
    now,
    I construct the stub each time I have to call the target method, and I'm wondering
    if
    I just cache the stub and keep calling the target method each time, will the underlying
    HTTP session be reused ? Any ideas ?
    Currently, if I do netstat on my Sun Solaris box (where this runs), I see the
    TCP
    connection being recreated during each invocation ...
    -john

    Hi John,
    You can do multiple invokes on the same stub. There is no
    need to create a new one for each invoke.
    WLS 7.0 use HTTP 1.0 with keep alive. If the server respects
    HTTP keep alive, then WLS will not create a new connection.
    HTHs,
    -manoj
    "john" <[email protected]> wrote in message news:[email protected]..
    >
    We're using WL7, and using the JAX-RPC API to access external webservices.
    Basically, we create the appropriate 'stubs' from the target WSDL using
    clientgen. Then we invoke the target method. Code looks something likethis:
    >
    Client_Impl client = new Client_Impl; // implementation of target
    ClientPort_Stub stub = client.getClientPort();
    stub._setProperty(javax.xml.rpc.Stub.ENDPOINT_ADDRESS_PROPERTY, url)
    stub.invoke(args);
    Now, when is the actual endpoint URL being created ? Is it when theinvoke()
    method is called ?
    It cannot be during the constructor since I pass the target URL after that...
    My problem is that I have to call the 'invoke' method quite frequently,and hence
    would like the HTTP session to be reused, rather than recreated each time.Right
    now,
    I construct the stub each time I have to call the target method, and I'mwondering
    if
    I just cache the stub and keep calling the target method each time, willthe underlying
    HTTP session be reused ? Any ideas ?
    Currently, if I do netstat on my Sun Solaris box (where this runs), I seethe
    TCP
    connection being recreated during each invocation ...
    -john

  • How to disable weblogic built-in HTTP session filter?

    Hi,
    I want to use my own HTTP seesion filter to manage HTTP session on weblogic clustered servers. It seems that weblogic servers plugin its HTTP session filter already for servlet. How can I use my own HTTP session filter to replace WebLogic built-in session filter?
    Thank you for your help.

    Could you be more elaborate on your requirement.
    Weblogic servers plugin provides a way to handle requests based on url content. or content type and so on, it dosent do much with users sessions other than for session stickyness.

  • Scope of component session and http session

    Hi,
    I wish multiple iviews to share the same information.  I am unsure however of the scope of portalcomponentsession, as opposed to http session. I have read the docs, and they are unclear as to the life and scope of these 2 sessions within portal.  Which one is tied to the user?  And which one is available over multiple iviews.
    I would appreciate any help with this
    Thanks
    Mariana

    Hi Mariana,
    > I am sorry
    No problem at all
    > I did not want to close the topic by mistake
    Just for explanation: If you give ten points (they call it blue, my eyes say black), this star is marked in the overview and somehow displaying "solved". In addtion, if you have marked a question as question, you can mark it as answered. As long as you don't do one of both things, you can reward points (2, 6) also in between without trimming your chances to get additional answers.
    > I did not de-mark the question,
    > I just replied to the post.
    When you initially opened the thread (that was no reply), it <i>seems</i> that you've de-marked this thread as question (the standard is: it is a question).
    Anyhow, some people seem to have made the experience that they definitely did not de-mark the thread as question, but it wasn't marked as question, anyhow.
    In this case, a short and friendly mail to [email protected] with the problem stated and alink to the thread concernced will help to repair everything...
    Best regards
    Detlev

Maybe you are looking for