Archive

Archive for the ‘Issues’ Category

Opalis: Invoke WebService – connection refused

February 10th, 2011 No comments

Let’s say you want to use a .NET webservice that works fine via Internet Explorer or SoapUI.
But when calling it from Opalis you get the error:  “Failed to invoke the Web Service method. The exception was “Unable to connect to the remote server. No connection could be made because the target machine actively refused it 127.0.0.1:5000“” The 5000 is the port number so this can be anything.

Not much to find on the web but the answer is very easy. (once you know it)
You need to be sure that the endpoint address in your web.config is a valid DNS name instead of http://localhost/

 <endpoint address=”http://FQDN/MyWebService.asmx” … />

Don’t forget to restart the website/webservice and clear your cache in Opalis!

Bug #600119: confirmed as bug (create user with random password)

November 17th, 2010 2 comments

Recently I reported a bug (see here) via Microsoft because I couldn’t create a new user with a password that was generated by a random string object. Well it is confirmed to be a bug in Integration Pack for Active Directory 2; it will be fixed in the next release.

Full info can be found on the Microsoft Connect site under bug 600119

Categories: Issues, Opalis Tags:

*Opalis Issue* Create AD user with random password fails

September 23rd, 2010 2 comments

I have already submitted this to CONNECT but I’m posting it anyway in case more people have the same issue and looking for answers. (Bug ID 600119)

Cannot set “UserPassword” value from a random generated string object. Hard coding a password works, tried all combinations and even up to 20 characters

Error message
– The server is unwilling to process the request. (Exception from HRESULT: 0x80072035) Command Executed [$pwd=ConvertTo-SecureString -string “*******” -asPlainText -force
– $connection=Connect-QADService -Service “POC-dc1” -ConnectionAccount “xxdomainxxAdmin” -ConnectionPassword $pwd
– Set-QADUser -Identity “CN=J324387,CN=Users,DC=DOMAIN1,DC=net” -UserPassword “*****” -Connection $connection] Command Executed [$pwd=ConvertTo-SecureString -string “*******” -asPlainText -force
– $connection=Connect-QADService -Service “POC-dc1” -ConnectionAccount “xxdomainxxAdmin” -ConnectionPassword $pwd
– Set-QADUser -Identity “CN=J324387,CN=Users,DC=nextclient,DC=net” -UserPassword “*****” -Connection $connection] Please make sure you have Powershell and Quest Active Directory command installed on the Opalis Action Server

What feature is this bug related to? Integration Pack

How often does this happen? Always Happens (consistent)

Have you seen this before in the product? I don’t know if this issue existed previously

Reproduction Steps – please list in detail the steps required to reproduce this issue.

Create new policy –> add create user object –> add create random string object -> specify 10 characters (capital, small, numbers, …) -> add reset user password and select password from the random generated string object

Opalis Integration Pack for Microsoft Active Directory v6.1

Categories: Issues Tags: , , ,