Having issues signing in

[PaulV]

Having issues signing in bought the Backyard Nikon 2.1.2 Premium, then an error pops up "License Validation Error Invalid Namespace" click ok "then my license Number pops up and blank identifier" i fill in my identifier and then Invalid Namespace.

Do you know the issue and how to correct this.  Thanks Paul   paul.vezina@hotmail.com

 

[admin]

Hi Paul,

This looks like an installation issue.  Is this a new installation on a new computer?

[PaulV]

No was installed about a year ago. Used this in July 2021 no problems now trying to get back in the error message keeps popping up

[admin]

Please re-install and try again.

[PaulV]

Uninstalled the existing application, and downloaded the updated version and still that error message shows up asking for my identfier and it doesn't recognizes the name, although my license

number shows but it will not boot up. it appears a glitch in the software?

[astroman133]

When you log onto this web site with user name PaulV do you see your license key under My Purchases | Orders?

If it were a glitch in the software there would be dozens of users reporting the same thing. So far, it is only you who have this issue.

[admin]

You need to enter your key and identifier exactly as they appear here on the website, under "My Purchases -> Orders". The identifier is case-sensitive.

https://www.otelescope.com/clients/orders/

Your identifier is your username, PaulV.

Are you still getting the same Namespace error message when you enter PaulV as your identifier?

Regards,

[PaulV]

On 1/30/2022 at 12:15 PM, astroman133 said:

When you log onto this web site with user name PaulV do you see your license key under My Purchases | Orders?

If it were a glitch in the software there would be dozens of users reporting the same thing. So far, it is only you who have this issue.

Well I feel Im unique then, because yes I see my license under my purchase /Orders and it is the same on the error code. It simply will not recognize the user name

[PaulV]

On 1/31/2022 at 4:59 AM, admin said:

You need to enter your key and identifier exactly as they appear here on the website, under "My Purchases -> Orders". The identifier is case-sensitive.

https://www.otelescope.com/clients/orders/

Your identifier is your username, PaulV.

Are you still getting the same Namespace error message when you enter PaulV as your identifier?

Regards,

Yes I am still getting the same error code. Verified everything all is according to My purchases / Orders  type PaulV still an error code

[admin]

Please download and try 2.1.3 release candidate from the pre-release download section. 

 

 

 

[PaulV]

Downloaded Version 2.1.3 uninstalled existing version then installed 2.1.3 the error appeared once more. So I am wondering if I can change user name for the license i have?
 

[astroman133]

The license key is tied to your username. If you see the key under My Purchases -> Orders when you log on as PaulV then that should be all that you need. Hopefully Guylain will have a path forward to suggest.

[PaulV]

20 hours ago, admin said:

Please download and try 2.1.3 release candidate from the pre-release download section. 

 

 

 

 

[PaulV]

See above error message after installing Version 2.1.3 this happened with the previous version as well. Previously mentioned I wonder if the program decided to not accept my license # ?

Since in My Orders it is correct license.

[astroman133]

"Invalid Namespace" seems like a more serious error. Perhaps a problem with some part of Windows or .NET that BYN uses. Have you tried installing BYN on another computer?
 

[admin]

How old is this computer? I suspect it's a lower level issue trying to decrypt the activation key.

[PaulV]

On 2/4/2022 at 5:16 AM, admin said:

How old is this computer? I suspect it's a lower level issue trying to decrypt the activation key.

It's about 4 years i7  old I'll try Rick's suggestion on my wife's laptop and let you know.

[PaulV]

Ok, well I downloaded on my wife's computer it ask for my license number then my identifier and guess what it works. So, I uninstalled, and re-installed, the program did not ask for my license

and of course the error came up, once you click ok, same thing happens my license number appears then asks for my identifier. and of course it brings up invalid user. Does this means I wil have to purchase another package?

[astroman133]

I am confused. Where did you uninstall and reinstall? Your computer or your wife's computer?

Did you reinstall in the same folder? Try reinstalling in a different folder.

[admin]

20 hours ago, PaulV said:

Ok, well I downloaded on my wife's computer it ask for my license number then my identifier and guess what it works. So, I uninstalled, and re-installed, the program did not ask for my license

and of course the error came up, once you click ok, same thing happens my license number appears then asks for my identifier. and of course it brings up invalid user. Does this means I wil have to purchase another package?

I'm confused... so much thing hapenning here, I can't make sense of the steps you took.

 

[chi_jayhawker@yahoo.com]

I am also having this issue. I'm getting an "invalid class". I've tried setting the permissions on the folder. I've tried to install to a new directory. I'm attempting to run BYN2.1.2.

[astroman133]

I would suggest downloading latest pre-release of BYN 2.1.3 to see if that has fixed the "invalid class error".

[chi_jayhawker@yahoo.com]

I tried installing the 2.1.3 version to no progress. I'm attaching an image of the WMI failure referenced in another thread. 

[astroman133]

What version of Windows are you running? I know that Microsoft has some issues with WMI to the point that ASCOM changed some internal functionality that relied on WMI that was broken.

[chi_jayhawker@yahoo.com]

The answer to that.

I'm also trying some things from this Microsoft page.

https://techcommunity.microsoft.com/t5/ask-the-performance-team/wmi-rebuilding-the-wmi-repository/ba-p/373846

[chi_jayhawker@yahoo.com]

Wow...found the fix. Following the instructions on that link I provided to the Microsoft site. I ran their script (pasted below) from an admin cmd prompt, and then rebooted.  And wah la....BYN started just fine. Use the script at your own risk, but that's all I had to do. Ran, and rebooted.

 

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
%systemdrive%
cd %windir%\system32\wbem
for /f %%s in ('dir /b *.dll') do regsvr32 /s %%s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
for /f %%s in ('dir /s /b *.mof *.mfl') do mofcomp %%s

[astroman133]

Thanks for letting us know.