Skip to main content
Solved

Missing Assembly Reference after Upgrade from 21R2 to 22R2

  • February 26, 2023
  • 6 replies
  • 117 views

aaghaei
Captain II
Forum|alt.badge.img+10

Hello all,

I am upgrading my Customization Projects to 2022R2. All references work fine just on “PX.DBServices” I am getting the below screenshot error. But as you can see I have already added the required reference. Any thought on what other library I should possibly add?

 

Best answer by Shawn Burt

Last time I had this happen it was because the reference was to the wrong px.dbservices I would remove the reference and readd it from the bin folder of your current instance.

View original
Did this topic help you find an answer to your question?

6 replies

Shawn Burt
Jr Varsity I
Forum|alt.badge.img+1
  • Jr Varsity I
  • 109 replies
  • Answer
  • February 26, 2023

Last time I had this happen it was because the reference was to the wrong px.dbservices I would remove the reference and readd it from the bin folder of your current instance.


aaghaei
Captain II
Forum|alt.badge.img+10
  • Author
  • Captain II
  • 1204 replies
  • February 26, 2023

Thanks, @Shawn Burt I have already done this. I even removed all references and added all again but no luck.


Shawn Burt
Jr Varsity I
Forum|alt.badge.img+1
  • Jr Varsity I
  • 109 replies
  • February 26, 2023

Sorry. I am not by a computer to check this out further tonight. I will check in the morning.


aaghaei
Captain II
Forum|alt.badge.img+10
  • Author
  • Captain II
  • 1204 replies
  • February 26, 2023

Appreciated @Shawn Burt 

I am rebooting my IIS and clearing temp files and caches … it might also help. If I find something I will post an update here


aaghaei
Captain II
Forum|alt.badge.img+10
  • Author
  • Captain II
  • 1204 replies
  • February 26, 2023

I did some cleanups and resets and restarts and fixed it somehow. I am not sure what was the root cause. It just wanted to drive me crazy. 


Shawn Burt
Jr Varsity I
Forum|alt.badge.img+1
  • Jr Varsity I
  • 109 replies
  • February 27, 2023

I have had the asp.net temporary files get “stuck” with a specific dll and not be able to unload the dll to allow it to be updated so it keeps generating an error similar to yours. reboot typically fixes it. Glad things are resolved :)


Reply


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings