Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

"License not found" message when trying to create an issue from outlook

Aaron Steinmetz
Contributor
November 27, 2013

Hi,

today we received the new Outlook2jira plugin license. After installing both plugins (for outlook and jira) and entering the license number we configured the setting in outlook. Testing connection was successful. Unfortunately we get the error "License not found" when we try to create a new issue from outlook.

Jira version:

Atlassian JIRA (v6.0.6#6105-sha1:9713ad1)

OS: Window 7

Outlook 2010 English

License info:

Version:0.3
Add-on key:de.catworkx.jira.plugins.outlook2jira
License details:Unlimited-user community license, Standard, expires 27/Nov/14
License status:Valid

Thanks

3 answers

0 votes
catworkx GmbH
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 31, 2014

Outlook2Jira v1.5.5 now validates the URL in the connection settings and thus does not allow the full SOAP URL here.

0 votes
Aaron Steinmetz
Contributor
December 3, 2013

Thanks Bonito,

The problem has been solved now. There is a part in the outlook plugin setting where you test the connection by using the correct jira URL. The URL I used to test the connection had the postfix "/rpc/soap/jirasoapservice-v2?wsdl". Although this URL was wrong the conncetion test was successful. After I entered a the jira URL without that postfix, it started working without any problem.

0 votes
Benito Picarelli
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
November 27, 2013

Hello Aaron,

I'm not very familiar with this problem that you are experiencing, but I found another answer that might help you.

https://answers.atlassian.com/questions/145609/on-outlook2jira-plugin-in-outlook-test-connection-passed-but-still-have-licenseresult-0

Apparently what solved the problem for him was updating the Universal Plugin Manager (UPM) to it's latest version (2.9) Could you please check what version is yours at?

Thanks!

Benito Picarelli

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events