Getting error in campaign- You are not authorised to use SQL Expressions.'IsIMSLoggedIn' cannot be processed | Community
Skip to main content
S
Senthil24
New Participant
January 6, 2017
Solved

Getting error in campaign- You are not authorised to use SQL Expressions.'IsIMSLoggedIn' cannot be processed

  • January 6, 2017
  • 16 replies
  • 7532 views

Hi,

I am learning how to use Adobe Campaign tool and while I was working on that I had a requirement of importing few packages using Adobe Campaign package feature for Creating External Instance.

After the package import I am facing this issue of a particular type of error- You are not authorised to use SQL Expressions.'IsIMSLoggedIn' cannot be processed. (see attachment). I dont know the reason for it but this has cropped up after the package import.

Anyone has any idea why this errror is showing up and how to resolve it. It will be very helpful.

Thanks.smiley

    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 Adhiyan

    Hi Senthil,

     

    I checked the screenshot , your Console is 8601 and server is 8720. So even if version is same the builds are different.

    Please upgrade your client to 8720 as well and the error will not appear.

    The reason is that some components of the server was upgraded and when you use the old client it's not able to properly view the changed components. 

    16 replies

    S
    Senthil24Author
    New Participant
    July 4, 2017

    Thanks everyone. Yes now we are running application server and build 8766 and this error has not cropped up again.

    florentlb
    florentlb
    New Participant
    January 25, 2017

    Hi Senthil,

    Did you manage to get an up to date console and resolve your issue?

    Florent.

    S
    Senthil24Author
    New Participant
    January 11, 2017

    Adhiyan wrote...

    Hi Senthil,

    Let me know if this solves the issue

     

    Hi adhiyan, 

    I have informed about this build version upgrade to my supervisors here. Since this is a training environment, upgradation might take some time, I am not sure when that will happen .

    When it gets done, I will let you know for sure. Thanks for helping. :) 

    Note: This error pops up many times, but except for that it hasn't actually disrupted any of the workflows or deliveries.  

    Adhiyan
    Adhiyan
    Employee
    January 10, 2017

    Hi Senthil,

    Let me know if this solves the issue

    S
    Senthil24Author
    New Participant
    January 10, 2017

    Adhiyan wrote...

    Hi Senthil,

    You can use the same link to install the client of build 8720 . Once you put in https://<campaign instance>/nl/jsp/logon.jsp in the browser you should be re-directed to download the same client version as the server . Once you install it just launch the nlclient.exe and login and check the server and client version

     

    Thanks adhiyan.

    Adhiyan
    Adhiyan
    Employee
    January 10, 2017

    Hi Senthil,

    You can use the same link to install the client of build 8720 . Once you put in https://<campaign instance>/nl/jsp/logon.jsp in the browser you should be re-directed to download the same client version as the server . Once you install it just launch the nlclient.exe and login and check the server and client version

      S
      Senthil24Author
      New Participant
      January 10, 2017

      florentlb wrote...

      I think the issue is indeed happening because of the version mismatch between console and server (8601 vs. 8720 is really big difference - lots of builds in between that have required console update).

      Just in case, you should be able to add named rights to operators from the operator details under Administration > Access management > Operators. Click Edit, then go to the Access rights tab. From there, you should be able to add the named right. See screenshot attached.

       

      Florent

       

      Thank you so much florent.

      florentlb
      florentlb
      New Participant
      January 10, 2017

      I think the issue is indeed happening because of the version mismatch between console and server (8601 vs. 8720 is really big difference - lots of builds in between that have required console update).

      Just in case, you should be able to add named rights to operators from the operator details under Administration > Access management > Operators. Click Edit, then go to the Access rights tab. From there, you should be able to add the named right. See screenshot attached.

       

      Florent

        S
        Senthil24Author
        New Participant
        January 10, 2017

        florentlb wrote...

        Hi Senthil,

        The URL you mentioned should offer you the possibility to install the right console. If not, contact the person in charge of upgrading the server to request that the right version of the console is made available, as explained here: https://docs.campaign.adobe.com/doc/AC6.1/en/INS_Installation_for_Windows__Client_console_availability.html

        Hope this helps,

        Florent

         

        Thanks florent,

        I will see about upgrading the client console ,however I wanted to ask you about the named rights issue that you mentioned earlier. Did you check that one? Do you think there might be an issue with that as well?

        Or the problem occurs because of build mismatch?

        florentlb
        florentlb
        New Participant
        January 9, 2017

        Hi Senthil,

        The URL you mentioned should offer you the possibility to install the right console. If not, contact the person in charge of upgrading the server to request that the right version of the console is made available, as explained here: https://docs.campaign.adobe.com/doc/AC6.1/en/INS_Installation_for_Windows__Client_console_availability.html

        Hope this helps,

        Florent

        Show more replies
        Terms & ConditionsAccessibility statement

        Loading footer...