Home
Reply
Contributor
bdharris
Posts: 6

University license R22 license/registration error

Hi,

I'm having a similar problem as this post. When trying to build my "sample app" using VS2010, I received error 4000 which led me to posts about having to register my app (since I'm on a University license) as mentioned in vik's post. While registering my app using the utility, I received the error "Registered. Error writing node registry." (same as first linked post) I also tried upgrading my user privileges, but the error didn't change.

And now running the app:

  out.get_message_text(): "Third party component has not been registered."

  out.get_log_info():

 

1
3
1 ALKI 4583
3 UserInfo 2
6 CurDate 2012/04/16
1 CurVersion 22
2 LogErrMsg 35 Registry data could not be accessed

 

I'll attach the (identifying info edited) error message from the registration application as well.

 

Thanks,

Ben Harris

 

 

 

Spatial Moderator
ybiyani
Posts: 231

Re: University license R22 license/registration error

Hello Ben,

 

Can you try the sample with R22SP2 and I recall this issue was addressed in that version?

 

Regards,

Yogesh

Contributor
bdharris
Posts: 6

Re: University license R22 license/registration error

We just recently starting using ACIS, so our example app is using R22 SP2. Is there any more information I can provide to help diagnosis?

Thanks

Ben

Contributor
bdharris
Posts: 6

Re: University license R22 license/registration error

Update: I just tried updating to the most recent R22 SP2 hotfix, and the problem persists. I'm starting to suspect that there's some problem with writing to the registry from my user account, but I've already upgraded to administrator (and running everything in administrator mode) with no change. For now I'll be exploring the problem from that angle.

Thanks,

Ben

Contributor
bdharris
Posts: 6

Re: University license R22 license/registration error

Update 2: Turns out the problem was much simpler than I realized: the registration utility needed to be run in Administrator. Doing so solves the problem.

Thanks for the help,

Ben