Error “Object reference not set to an instance of an object” when check out file

Semua Balasan

• 04 Februari 2012 20:57

   

   
  

  0

  Are you having the issue when you access http://oldcompanyweb or when you access http://companyweb? Or for both of them

  Have you extended the web application http://oldcomanyweb to Intranet zone or have you added manually that http://companyweb link in AAM?

  If the issue is present only for http://companyweb url and if you have added it manually in AAM, then delete it and extend your web application to intranet zone.

  Here you have some information regarding AAM http://technet.microsoft.com/en-us/library/cc261814%28office.12%29.aspx Plan alternate access mappings (Office SharePoint Server)

  ---

  MCITP|MCTS SharePoint| SharePoint Performance blog
  • Balas
  • Kutip

   
• 06 Februari 2012 11:31

   

   
  

  0

  Hello,

  Since you are getting ASP.NET Runtime error "Object Reference Not Set To Instance" in SharePoint, i would recommend to check SharePoint Log files and Windows Event Viewer to identify what's the error is.

  ---

  Anand Thurubatla, AT&T Hosting & Application Services
  • Balas
  • Kutip

   
• 07 Februari 2012 3:23

  Moderator

   

   
  

  0

  Hi grace,

  Here is an article with more detailed steps, check the web application with issues from AAM and specify the URL in Intranet zone, you can check from below:

  http://yagyashree.wordpress.com/event-id-8214-object-reference-not-set-to-an-instance-of-an-object/

  Thanks

  ---

  Daniel Yang

  TechNet Community Support

  

  • Balas
  • Kutip

   
• 09 Februari 2012 23:08

   

   
  

  0

  Hi,

  Thank you for your reply. We upgraded Sharepoint 3.0 from 2.0 a while ago. In the process of upgrading, I remembered I created http://oldcompanyweb for some reason. Now http://oldcompanyweb doesn't work, however http://companyweb works.

  The internal site addres is http://companyweb, the external website address is https://www.mycompany.com:987. I don't understand why https://www.mycompany.com:987 is in default zone, http://companyweb is in Intranet zone in AAM.

  Please advice!

  Grace

  ---

  grace

  • Balas
  • Kutip

   
• 09 Februari 2012 23:20

   

   
  

  0

  Hi Daniel,

  Thank you for you reply. I am comfused by the last third steps. It said

  –>You need to specify the URL which is giving you problem in the “Intranet” zone. So it will see like this:

  Default: http://matrix

  Intranet: http://yagyashree.org

  In my case, I have

  Internal URL                                                 Zone                         Public URL for Zone
  https://www.mycompanyweb.com:987       Default                   https://www.mycompanyweb.com:987
  http://companyweb                                     Intranet                    http://companyweb

  How should I make the change here?

  Please advice!

  Thanks,

  Grace

  ---

  grace

  • Balas
  • Kutip

   
• 10 Februari 2012 7:58

   

   
  

  0
  Are you using SBS2008?

  ---

  MCITP|MCTS SharePoint| SharePoint Performance blog

  • Balas
  • Kutip

   
• 10 Februari 2012 18:59

   

   
  

  0

  Hi Bogdan,

  Yes, I am using SBS 2008. Does SharePoint work differently in SBS 2008? Please advice!

  Thanks in advance!

  Grace

  ---

  grace

  • Balas
  • Kutip

   
• 12 Februari 2012 10:04

   

   
  

  1
   

  SBS is configuring automatically SharePoint (IIS ports, AAM, Application pool) using his own standards and connects it to SBS console.

  In SBS console are you having any issues with SharePoint site?

  Could you please paste the error message from event viewer, Event ID 8214?

  ---

  MCITP|MCTS SharePoint| SharePoint Performance blog

  • Balas
  • Kutip

   
• 17 Februari 2012 9:46

   

   
  

  0

  There are various reasons why you would get object reference not set . I had my love affair while creating a site collection. Please refer to the below article may help in your pursuit.

  http://sp-vinod.blogspot.com/2012/02/cannot-create-site-collection-error.html

  First place I would start as most of us do is ULS logs, event viewer that should define a path to troubleshoot the issue.

  You may notice if you create a new web app and try checkout it will work but for the original web app it may still have the issue.

  If I were you and didnt have any bespoke solutions deployed quickest way to test is to create a new web app  and detach the content db from web app where you're having the issue and attach the content db to the new web app. You may need to schedule a downtime while doing this. Its good to test it in the test environment provided you can replicate the issue

  • Ditandai sebagai Jawaban oleh Wayne Fan 20 Februari 2012 11:33
  •  
  • Balas
  • Kutip