Access Package Share from Local Instance | Community
Skip to main content
joshuausdavin
Level 3
Jul 6, 2017 6:01 PM UTC
Solved

Access Package Share from Local Instance

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.
    kautuk_sahni
    kautuk_sahniAccepted solution
    Employee
    Jul 7, 2017 7:31 AM UTC

    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
    View reply

    7 replies

    satyajits312357
    New Participant
    Sep 17, 2018 11:51 AM UTC

    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

    Translate
    bobkranson
    Level 4
    Oct 6, 2017 6:47 PM UTC

    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

    Translate
    bobkranson
    Level 4
    Oct 6, 2017 6:42 PM UTC

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

    Translate
    bobkranson
    Level 4
    Oct 6, 2017 6:28 PM UTC

    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>
    Translate
    joshuausdavinAuthor
    Level 3
    Jul 7, 2017 11:18 AM UTC

    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.

    Translate
    kautuk_sahni
    kautuk_sahniAccepted solution
    Employee
    Jul 7, 2017 7:31 AM UTC

    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

    Translate
    Kautuk Sahni
    leeasling1
    Level 3
    Jul 6, 2017 6:10 PM UTC

    The external link is Welcome

    Translate
      Terms & ConditionsAccessibility statement

      Loading footer...