DB Migration for sql 2000 to sql 2008 using upgrade advisor tool

I have recently upgraded from VS 2008 to VS 2010 and the conversion process completed successfully.  However, when viewing my design view for all aspx pages, any control i had in there is displayed with the message "Error Creating Control - Object Reference not set to instance of an Object".  If i even attempt to create a simple new button or textbox from the toolbox, the control automatically comes back with that error.  However, in runtime, my controls are all displayed and functioning correctly.

I have seen some posts regarding session state and checking that Context is not null in the OnInIt override method, but I am no using any OnInIt override methods in any of my code behinds.  It pretty standard with usually only page loads.

This is creating a tough time developing because it is not using intellisense when i am looking for events and other actions on the controls.  Also, Javascript does not appear to be functioning the same  since it doesnt seem to be using the FindControl method correctly (Probably because the page is building out the control).

This is very frustrating and i've spent two days on this, so any help would be appreciated.

Thanks! 

My existing system has Visual Studio 2008 and Visual Web Developer 2010 Express. But Microsoft web installer for Webmatrix has made Wematrix Launch ribbon menu pointing to Visual Studio 2008. How could I make Webmatrix point to Visual Web Express 2010. To make use of IntelliSense and the debugger, I have to manually launch Visual Web Developer 2010 Express.

Any help to resolve this would be helpful Or is this a known issue at this time!

What version of the Enterprise Library should be used with Visual Studio Developer Express 2008?

Looking at using the Data Access Application Block.

Currently using an earlier version in C# that doesn't seem to be closing connections properly.

Tim

Hi We are migrating our MOSS environment to new hardware (same domain). We have successfully migrated the SSP and the main site - they appear to be working fine. When I try to attach the mysites content DB (restored in SQL) the mysites are missing. Under application management -> content databases the 'current number of sites' is 0. SSP mysites settings look ok (we are using a different URL for the mysites). Can anyone shed any light? Cheers Mike

Hi all, 

I am trying to install AKS 1.1 (not 2 or 1.0 cuz thats the only release i was able to find on aks.hisoftware.com) on a windows server 2008 x64bit machine. 
 
the toolkit installs in this location: C:\Program Files (x86)\HiSoftware\AKS  .... but nothing in the 12\template\features folder.

the script install_AKSFEAT.bat refers to a feature name "AKS", but i cannot see the feature anywhere in the features folder, and i cannot see a WSP pacakge to deliver this feature to sharepoint!

i event tried to look for the feature manifest to reverse engineer the works of the feature but no luck finding this file in the AKS install folder.

what am i missing here? how can i get AKS 1.1 to install properly and the feature to activate? please HELP!!

---

- mutaz

when I do a content migration from source site to destination, I set the Hidden navigation items in the source site, but after content migration, the navigation site didn't hidden and displayed, in a short word the naviation not being persisted with a content deployment. how can i fix it?

I have a portal in sps 2003 and needs to migrate to MOSS 2007.

I have tried in below ways but it was not success.

1. one way i have tried with import/export but i have not found import/export commands in sharepoint 2003.

2. second way i have tried database migration for this i am getting below error.

The specified SPContentDatabase Name Parent=SPDatabaseServiceInstance is too old to be upgraded by this version of SharePoint. Please perform the needed intermediate upgrades before attempting this one

i have run prescan tool also before database migration but  still i am getting this erro.

How can i proceed this activity please help.

 

Hello,

While going through all that is needed to be done for a MCMS 2002 migration to MOSS 2007. I have been doing the analyze part from central administration on the test MCMS 2002 database.  I've fixed up all errors but one which has to do with 'Leaf names are not unique.' No problem except when I open Site Manager and click the Resource Gallary area, I get the following error message.

Error: 1002
Description: The XML parser could not parse the file it was given.
Severity: 5
Source: Source: GrammarParserC.dll aegrammarparser.cpp 319

Debug info: Request is too big
Extra info:
Client Source: AETree::tvChanTree_Expand
Recommended Action:

Because of this error, I'm unable to navigate the Resources tree node, which would enable me to delete or at least rename the duplicate name.

Any thoughts or ideas on how to get pass this error? Or, how to remove the duplicate resource folder so I can get pass the migration error message?

Thank you.

I'm sure this is a common question but I can't seem to find any guidance.

What is the accepted approach to migrating your dev/UAT environment to Production?  We are moving structural changes, new infopath forms and event handlers, but we want to preserve the content already existing on production.

We have some 700 submitted forms on production using v1.0 of our form template.  We now have v2.0 of the form template on UAT, along with sharepoint changes such as workflows and views that we want to push to production via backup/restore.  This would overwrite the submitted forms on prod that we want to keep and use with v2.0 of the template. 

It seems if I copy the forms then try to copy them back I run into a bunch of issues.  Some stem from addition of columns or fields in the IP form, some could be version differences, list guids.... a lot can go wrong.

Whats the best way to accomplish this without the least amount of headache?  Is there a widely accepted approach?

---

http://lbellows.blogspot.com http://www.ptreviews.net

HI,

I have a Sharepoint Server 2007 and is going thru a domain migration from domainA.com to domainB.com

Other than mapping all the users with the new domain, any other things i should take note?

 

Thanks