Connect-msolservice error

Question

Dear Support,
can you please advise how to properly troubleshoot Connect-MSOlService? I have x64 Adaxes installation
I have this function properly working in Powershell ISE and Powershell console on the Adaxes server, but when I try to run it in PS script inside Adaxes - I get a 1 minute wait and then "Object reference not set to an instance of an object".

I have Microsoft Online Services Sign-In Assistant install from https://www.microsoft.com/en-us/downloa ... x?id=28177

I have MSOnline module installed via Powershell.
Version Name Repository Description
------- ---- ---------- -----------
1.1.183.17 MSOnline PSGallery Microsoft Azure Active Directory Module for Wind...
Powershell version 5.1

Thanks for any advise!

Comments

Hello Dmytro,

Could you, please, post here or send us (support[at]adaxes.com) the script you are using in Adaxes. A detailed description of the script usage will be also appreciated.

What version of Microsoft .NET Framework is installed on the computer where Adaxes service runs?

What version of Adaxes you are currently using? To check the version:

1. Launch Adaxes Administration Console.
2. In the Console Tree, right-click your service.
3. In the context menu, click Properties.
   
4. Adaxes version will be displayed on the General tab.
   

---

Hello,
Adaxes version is 3.11.16721.0
.NET Framework 4.6.2
Code is standard:

$Usr = "XXXXXX"
$Pwd = ConvertTo-SecureString -String "XXXXXX" -AsPlainText -Force
$Credential = New-Object -TypeName System.Management.Automation.PSCredential($Usr, $Pwd)

connect-msolservice -Credential $Credential

---

Hello Dmytro,

Thank you for the details. The script should work just fine. Could you, please, clarify how exactly the script runs in Adaxes? In what format do you specify the username in the $Usr variable?

---

I specify it as upn - xxx@xxx.com.
This script is actually working in Powershell ISE open on server, but not from console on same server.
But access to internet from server is via proxy.

---

Hello Dmytro,

Could you, please, post here or send us (support[at]adaxes.com) the full script and clarify how it is executed (by a Custom Command, a Business Rule or a Scheduled Task)? A screenshot of the command/rule/task would be much appreciated.

---

Hello!
I'm just running code directly via Powershell editor.

and at the same time same code, copy/paste from PS ISE on same server

---

Hello Dmytro,

Thank you for the clarification. For troubleshooting purposes, could you, please, enable tracing of requests sent to Office 365, reproduce the issue and then check the log file? For information on how to enable the tracing, have a look at the following help article: https://www.adaxes.com/help/?HowDoI.Per ... uests.html. If you are not sure, you can send the log file to us (support[at]adaxes.com).

Also, could you clarify if the Office 365 tenant which you try to connect to via the script is registered in Adaxes and works fine?

---

Hello,
after changing config file - the log doesn't appear while running this code. So it doesn't even send the request, I guess
No, this tenant is not registered in Adaxes, but it works fine :)

---

Hello Dmytro,

No, this tenant is not registered in Adaxes, but it works fine

Could you, please, try to register the tenant in Adaxes? For details, have a look at the following tutorial: https://www.adaxes.com/tutorials_Active ... htm#tenant.

after changing config file - the log doesn't appear while running this code. So it doesn't even send the request, I guess

The log does not appear because the tenant is not registered in Adaxes.

---

Hello,
Unfortunately I can't since I don't have admin priveleges in Azure tenant, I'm managing only on-premise AD. But we really need to pull the license info to adaxes.
Is there any other way to troubleshoot this?

---

Hello Dmytro,

“Object reference not set to an instance of an object.” is a very common error and can occur because of multiple reasons. To troubleshoot the issue, you need to register a tenant in Adaxes. It is not necessarily should be your production tenant. You can create a dummy tenant in Office 365 and then register it in Adaxes without association with any scope of your domain.

---

Hello,
I've created a test tenant and tried to add it. The irony is that I get same error message :lol:

![]()

Answer 1

Dear Support,
thanks for your help - we've found the issue. Proxy had to be set up manually under service account - settings set up in Adaxes configuration (proxy) - didn't work.