<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Login issue with SIM 4.1 in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/login-issue-with-sim-4-1/m-p/3370858#M5643</link>
    <description>I have experienced something like that, made a link from our intra (&lt;A href="https://host.name.com:50000/login.jsp)" target="_blank"&gt;https://host.name.com:50000/login.jsp)&lt;/A&gt; and sometimes I got an error like yours and sometimes I had to login twice before I got in. Corrected the link to go to &lt;A href="https://host.name.com:50000/" target="_blank"&gt;https://host.name.com:50000/&lt;/A&gt; and the problem was solved.</description>
    <pubDate>Thu, 09 Sep 2004 08:26:52 GMT</pubDate>
    <dc:creator>DeadUserIDBR829846</dc:creator>
    <dc:date>2004-09-09T08:26:52Z</dc:date>
    <item>
      <title>Login issue with SIM 4.1</title>
      <link>https://community.hpe.com/t5/server-management-systems/login-issue-with-sim-4-1/m-p/3370857#M5642</link>
      <description>I just completed the SIM 4.1 upgrade and finished the patch to get past the java hanging logon issue.  Once I did I got the following error message when trying to go in from my computer and only my computer.  When I logon via terminal services to the server and when any other team members login they don't have any issues.  This issue occurs on my workstation no matter which user account I use to get in.  I have found a way to get around it by copying and pasting the link &lt;BR /&gt;https://Servername:50000/mxportal/home/MxPortalFrames.jsp or it even works (Sometimes) if I click on the back and forward buttons in my browser a couple of times.  Any suggestions.  &lt;BR /&gt;&lt;BR /&gt;Error message returned:&lt;BR /&gt;type Status report&lt;BR /&gt;&lt;BR /&gt;message /j_security_check&lt;BR /&gt;&lt;BR /&gt;description The requested resource (/j_security_check) is not available.&lt;BR /&gt;</description>
      <pubDate>Thu, 02 Sep 2004 08:41:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/login-issue-with-sim-4-1/m-p/3370857#M5642</guid>
      <dc:creator>Christopher_53</dc:creator>
      <dc:date>2004-09-02T08:41:09Z</dc:date>
    </item>
    <item>
      <title>Re: Login issue with SIM 4.1</title>
      <link>https://community.hpe.com/t5/server-management-systems/login-issue-with-sim-4-1/m-p/3370858#M5643</link>
      <description>I have experienced something like that, made a link from our intra (&lt;A href="https://host.name.com:50000/login.jsp)" target="_blank"&gt;https://host.name.com:50000/login.jsp)&lt;/A&gt; and sometimes I got an error like yours and sometimes I had to login twice before I got in. Corrected the link to go to &lt;A href="https://host.name.com:50000/" target="_blank"&gt;https://host.name.com:50000/&lt;/A&gt; and the problem was solved.</description>
      <pubDate>Thu, 09 Sep 2004 08:26:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/login-issue-with-sim-4-1/m-p/3370858#M5643</guid>
      <dc:creator>DeadUserIDBR829846</dc:creator>
      <dc:date>2004-09-09T08:26:52Z</dc:date>
    </item>
    <item>
      <title>Re: Login issue with SIM 4.1</title>
      <link>https://community.hpe.com/t5/server-management-systems/login-issue-with-sim-4-1/m-p/3370859#M5644</link>
      <description>Thanks for the response.  I had actually worked on it yesterday and figured out that my bookmark was pointing to a complete path.  I changed it and I haven't seen the problem since.</description>
      <pubDate>Thu, 09 Sep 2004 08:30:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/login-issue-with-sim-4-1/m-p/3370859#M5644</guid>
      <dc:creator>Christopher_53</dc:creator>
      <dc:date>2004-09-09T08:30:53Z</dc:date>
    </item>
  </channel>
</rss>

