Access Package Share from Local Instance | Community
Skip to main content
J
joshuausdavin
New Participant
July 6, 2017
Solved

Access Package Share from Local Instance

  • July 6, 2017
  • 7 replies
  • 5597 views

Should I be able to access package share from my local instance? After entering my credentials I'm getting the following error.  Also, what is the Adobe URL that contains all the cumulative fix packs?

HTTP ERROR: 500

Problem accessing /crx/packageshare/login.html/content/packageshare/tools/login.html. Reason:

    java.lang.NullPointerException

Powered by Jetty://

    This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
    Best answer by kautuk_sahni

    Unable to reproduce this on AEM 6.3.

    But it should be working. Try it with the fresh AEM instance in incognito mode and see if you still faces this issue.

    Where as mentioned by Lee, you can use Welcome .

    ~kautuk

    7 replies

    S
    satyajits312357
    New Participant
    September 17, 2018

    Hi;

    Getting the same issue while trying to access Package share from my local AEM instance of AEM 6.4...Tried all means and it does not allow to login . Not sure what's wrong when you access through your local instaces

    HTTP ERROR: 500

    Problem accessing /crx/packageshare/login.html/content/packageshare/tools/login.html. Reason: 

        java.lang.NullPointerException

    B
    bobkranson
    New Participant
    October 6, 2017

    Yep....looks like they did some maintenance while posting CFP12 for 6.1...

    Problem Summary:

    Availability Problems with Multiple Solutions - Multiple
    Services

    Severity:

    Severity 1

    Phase:

    Resolved

    Start:

    2017-10-05 22:10 MDT

    End:

    2017-10-05 22:44 MDT

    Duration:

    34 minutes

    B
    bobkranson
    New Participant
    October 6, 2017

    Grrrr.....service unavailable and restore announcement coming?

    B
    bobkranson
    New Participant
    October 6, 2017

    I've just began validating 6.3 and am having trouble getting CFP2 from anywhere....

    I am also having trouble with Package Share with AEM 6.3.  Looking through Adobe pages on their external website it seems they are not even offering https : // www.adobeaemcloud.com/content/packageshare/tools/login.html (had to add spaces so it wasn't automatically turned to 'Welcome' link).

    When I go to the aemcloud package share link today it is stuck, hang, doesn't work.  Yes I've tried private, incognito, clear caches, reboot machine, I even got a fresh coffee while the login seemed hung/waiting.  Is there news about using the Package Share with 6.3?  All documentation is saying to use the "Tools > Package Share" from within AEM -- and nobody checked that documentation because its "Tools > Deployment > Package Share".  (yes a little frustrated)

    Furthermore, when I look at the sources of the package share login from Tools > Deployment > Package Share, I see login/credential fields that are non-standard!  Where is j_username and j_password?

                    <tr>
                        <td><label for="psuser" >Username</label></td>
                        <td><input type="text" name="psuser" id="psuser"></td>
                    </tr>
                    <tr>
                        <td><label for="pspass">Password</label></td>
                        <td><input type="password" name="pspass" id="pspass" autocomplete="off"></td>
                    </tr>
    J
    joshuausdavinAuthor
    New Participant
    July 7, 2017

    I'm still getting the same error when attempting on a new 6.2 instance with SP1 and CFP4.  I'll use the link lasling​ mentioned but it would be nice if it worked via package share to avoid downloading, then uploading again to package manager.

    kautuk_sahni
    kautuk_sahniAccepted solution
    Employee
    July 7, 2017

    Unable to reproduce this on AEM 6.3.

    But it should be working. Try it with the fresh AEM instance in incognito mode and see if you still faces this issue.

    Where as mentioned by Lee, you can use Welcome .

    ~kautuk

    Kautuk Sahni
    L
    leeasling1
    New Participant
    July 6, 2017

    The external link is Welcome

      Terms & ConditionsAccessibility statement

      Loading footer...