UPSA Error in Server Farm

Question

Hi,

We are having issue in UPSA when Sharepoint app deployed at production server.

Environment : 2 WFE / 2 App / 2 DB - We have Dec 2011 CU installed.
Error :

Server Error '/'  Application

Object reference not set to an instance of an object

Description: An unhandled exception was generated during the execution of the current web request. please review the stack trace for more information about the error and where it orginated in the code.

Exception Details: System.NullReferenceException: Object reference not set to an instance of an object.

Source Error:

An unhandled exception was generated during the execution of the current web request.Information regarding the origin and using the exception stack trace below.

Stack Trace:

[NullReferenceException: Object reference not set to an instance of an object.]

     Microsoft.office.server.Administration.UserProfileApplicationProxy.get_ApplicationProperties()  +134

We tried the following article as suggested but still having the same error.

http://myspexp.com/2011/04/28/user-profile-synchronization-servicehangs-on-starting-i-fixed-it/

Any Help

Thanks

Answer 1

When is this error occurring?  The Event Log entry that you posted is helpful, but we also need to know the context of the error.  For example, is this error occurring once a day, or every time you try to navigate to the User Profile Service Application in Central Administration, or some other time?

---

Colorless Green Ideas Sleep Furiously http://www.sharepointnerd.com

Answer 2

Hi.

If you have issues with the UPS, then I recommend not trying to t-shoot it but redo it all using the proper measures.
Follow Spencer Harbars guide and it will work in the end. A lot of tweaks and special steps are needed in order to get it working.

Rational Guide to implementing SharePoint Server 2010 User Profile Synchronization
http://www.harbar.net/articles/sp2010ups.aspx

Follow his guide to the very letter and the UPS will work.

If you still want to try and get it working, Harbar even has a guide for that as well:

“Stuck on Starting”: Common Issues with SharePoint Server 2010 User Profile Synchronization
http://www.harbar.net/articles/sp2010ups2.aspx

Good luck

Regards

---

Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
Download the SharePoint Branding Project here

Answer 3

Hi.

If you have issues with the UPS, then I recommend not trying to t-shoot it but redo it all using the proper measures.
Follow Spencer Harbars guide and it will work in the end. A lot of tweaks and special steps are needed in order to get it working.

Rational Guide to implementing SharePoint Server 2010 User Profile Synchronization
http://www.harbar.net/articles/sp2010ups.aspx

Follow his guide to the very letter and the UPS will work.

If you still want to try and get it working, Harbar even has a guide for that as well:

“Stuck on Starting”: Common Issues with SharePoint Server 2010 User Profile Synchronization
http://www.harbar.net/articles/sp2010ups2.aspx

Good luck

Regards

---

Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
Download the SharePoint Branding Project here

This is a great point, but assumes that you can delete your User Profile Service Application and start over.  If you can safely do that, then this is your answer.

---

Colorless Green Ideas Sleep Furiously http://www.sharepointnerd.com

Answer 4

Hi Guys,

Thanks for all suggestions.

I have recreated UPSA so many times. Ensured all app pools (web service root) are running with farms account.

My top navigation bar is also corrupted

An error occured while rendering navigation for requested URL : /. Exception message: object

reference not set to an instance of an object. stack trace: at

I am stuck and running of time. Guys support

Answer 5

Hi BizTalkGhost.

If your top navigation is 'corrupted' then there are issues beyond the UPS. Do you have a custom Masterpage or CSS loaded? If you do, start by replacing the default V4.master(if that is the defasult for that site type) and remove any reference to a custom CSS. See if the issues go away.

Then, like Erik said, please tell us a little about the context, when is this happening and when doing what? Are there any more info in the logs at the time of the error?

The error message you gave us is too common...

Regards

---

Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
Download the SharePoint Branding Project here

Answer 6

Hi Thomas,

In our setup thru app server we are able to browse it perfectly. When opened the virtual IP (NLB) we get this error. Not only for our application even for the test site it is the same behavior.

Thanks

Vijay

Answer 7

In our case the issue was UPSA failed with timestamp error. Web front end servers clocks were not in sync with App servers. Once synced started working fine.

Thanks

Vijay