Soap exception

Oksana Boiko February 18, 2014

Hi,

Have a problem with access to Soap service.

https://nemling.atlassian.net/rpc/soap/jirasoapservice-v2 - exception

but it works ok other instances, for example https://jira.atlassian.com/rpc/soap/jirasoapservice-v2

What is the problem?

Thanks.

2 answers

0 votes
Oksana Boiko February 20, 2014

I aplogize for the mistyping and letting my emotions go high.

The time for the question to be appoved is way too long and it upsets that critial functions were not accessible and I had no reply.

Thanks for trying to help.

Sorry, for being nasty.

Sincerely.

0 votes
Joe Clark
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 18, 2014

Are you sure you have the URL correct? "nemling.atlassian.net" does not exist:

yeah-yeah:~ jclark$ wget https://nemling.atlassian.net/
--2014-02-19 09:32:51--  https://nemling.atlassian.net/
Resolving nemling.atlassian.net... failed: nodename nor servname provided, or not known.
wget: unable to resolve host address ‘nemling.atlassian.net’

Oksana Boiko February 19, 2014

Is this a joke??? If yes - well done then.

Never mind and don't bother. Anyway, I've never seen such useless reply. By the time my question was approved on your side (more than 8 hours passed) I got it resolved by another support memeber via support ticket. And what a surprise, he could find nemling.atlassian.net. It exists!

Joe Clark
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
February 19, 2014

I was just trying to help, there is no reason to be rude to me.

I went and had a look at the support ticket, and I see the problem! The correct URL is "nemlig.atlassian.net", but here in this question you said "nemling.atlassian.net", so it wasn't working for me and I couldn't try to reproduce your problem.

The question had to be manually approved because the automatic systems thought it might be spam - I'm sorry for this inconvenience, I have corrected this issue and it should not happen again for you.

I'm glad that the problem has now been resolved.

Suggest an answer

Log in or Sign up to answer