I've had this error a number of times at different places. On one database, it occurred when upgrading the avatars.
EXCEPTION: Object reference not set to an instance of an object.
at CommunityServer.Avatars.UpdateAvatar(Int32 userID, Stream postedFile)
at CommunityServer.Upgrader.FileUpgrader.UpgradeAvatars()
at CommunityServer.Upgrader.Part4.MoveFilesToCfs()
On the more recent database, I get this message:
EXCEPTION: Object reference not set to an instance of an object. at CommunityServer.Upgrader.FileUpgrader.UpgradePhotoGalleries() at CommunityServer.Upgrader.Part4.MoveFilesToCfs()
Maybe it's something with the database (this is a test database local to my machine that I haven't used in a while), maybe not. In any case, I'm not sure why this is happening. The errors all occur in Step 6: Move existing files into centralized storage.
Can anyone provide some clues?
What version of the upgrade tool are you using? Beta 1 or Beta 2?
Dave, it's Beta 2.
There were many updates to the upgrader for the RC and the final relase. Could you retry with the final release of the tool?
I get the same error:
4/16/2008 11:57:48 AM -- Upgrading photo galleries4/16/2008 11:57:48 AM -- EXCEPTION: Object reference not set to an instance of an object. at CommunityServer.Upgrader.FileUpgrader.UpgradePhotoGalleries() at CommunityServer.Upgrader.Part4.MoveFilesToCfs()
using the final release.
Any help would be greatly appreciated!
--Michael
Hi Michael - What version of CS are you trying to upgrade?
CS 2007, I believe the specific version is: CS2007_3.0.20510.895
Can you send me your full log file? ddonaldson AT telligent DOT com.
Hi Dave,
I started this thread. I haven't had time to try out some things posted here, like Ben's suggestion, but now I see the final release is available so I'll be trying that in a few days.
If you do figure out something about the "object reference not set to an instance of an object" problem, can you post some general troubleshooting ideas? With my luck, I'll run into the same problems when I try to upgrade to the final 2008 release, and I want to be ready.
Oh, and by the way, I'm upgrading from version 3.1.20917.1142.
I'm getting this exact error as well, upgrading from 2007.1 SP1.
Same for me.
Bump.
Could those experiencing this issue run the following SQL script against your database:
select count(*) as [Bad File Count]from cs_PostAttachmentswhere FileName is null
Does it report a value greater than zero? If so, the issue is caused by post attachments that don't have file names.
If the number isn't large, you could manually remove/rename these files, or, to update all of them with a new name, you can execute the following SQL script against your database:
update cs_PostAttachmentsset FileName = 'bad file'where FileName is null
Note that this may cause these files to be unviewable. If this is the cause of the problem, we have a way to fix the upgrade tool to support renaming the files more intelligently.
Mine shows 0.
As mentioned on a previous thread on this issue (that has no responses yet after several days) my installation is not our live one and is on a virgin machine with just 2007.1 installed.
dotnetdude:As mentioned on a previous thread on this issue my installation is not our live one and is on a virgin machine with just 2007.1 installed.
What do you mean by this?
Hi Ben,
We basically have a production environment where 2007.1 is running great. The install I am talking about is on a dev system where we play with new ideas before rolling them out.
To answer your questions :-
1) Yes, but very little - just a few posts.
2) Yes, perfectly.
3) Are you joking - you jump first ;-) (and im glad as the upgrade hasnt worked under test conditions)
4) N/A
Regards,James.
Copyright© 2008 Telligent Systems Inc. All rights reserved CommunityServer.com • Telligent.com