Support Forums

Exchange 2019 / Win…
 
Notifications
Clear all

Exchange 2019 / Windows Server 2019 / Fresh Install -> Invalid ObjectReference

5 Posts
2 Users
0 Likes
1,223 Views
Posts: 0
Topic starter
(@Anonymous)
Joined: 1 second ago

I repeated the installation three times with different options (virtual directories / app-pools)

– SQL Server 2017 Express – fresh
– Prepared Active Directory (Directory is also fresh)
– Exchange Server 2019 Standard – fresh

The setup runs without any notice. But I can’t login with my user (new user in domain admin group).

– Entering WRONG credentials = Permission denied = correct
– Entering CORRECT credentials = Invalid ObjectReference

There are no log entries.

Greetings, Ingo

4 Replies
Posts: 1563
Admin
(@jdixon)
Noble Member
Joined: 9 years ago

It is possible you skipped the step on configuring CloudPanel by going to the setting page: http://kb.knowmoreit.com/getting-started/install-cloudpanel/ (see Set CloudPanel Settings).

You need to access the /cloudpanel/admin/setup page from the server you installed CloudPanel on. It won’t require credentials and once you populate these settings with the correct values from your enviornment, then you should be able to login.

Reply
2 Replies
(@Anonymous)
Joined: 1 second ago

Posts: 0

@jdixon

Thank you. 

 

No. I had configured everything described on the  KB and the video (I realized, it’s an older video). The settings have been stored correctly.

I have noticed the following:

The value of the Exchange Version – in my case 2019 – is not stored as selected. It always jumps back to “2016” after reloading the settings. Perhaps only a display error, perhaps the reason. 

Reply
(@Anonymous)
Joined: 1 second ago

Posts: 0

@jdixon

I found the problem. Please take a look into your code when checking the “super admin” state while logging in.

I am using a localized version of Windows. The “Domain Admin” Group is called different. After correcting the entry it works. There must be an issue in checking the user and the admin groups. 

 

 

Reply
Posts: 1563
Admin
(@jdixon)
Noble Member
Joined: 9 years ago

It checks the name of the group in Active Directory. So if you group is called something different, you need to put that value in there.

Reply
Share: