Losing out custom metadata info of few documents of a document librarby when migrated from MOSS 2007 to Sharepoint 2010

We have recently migrated from moss2007 to sharepoint 2010.We have a document library containing large no. of documents in it & for those documents there are some custom metadata columns apart from OOB library columns . We have user content DB attach
migration and after that we can see blank value under the custom columns for some records. However interesting point is we can see this metadata is showing for few documents.
Please suggest.

Hi,
What is your Office edition? When we create a managed metadata column in a Document Library, it will prompt that ‘Earlier versions of client programs might not support this type of column’. You should use Office 2010 to edit and create a document then save
to document library .
For detailed information ,please refer to this article:
http://rules.ssw.com.au/SoftwareDevelopment/RulesToBetterSharePoint/Pages/2010-Managed-Metadata-with-Office-2007.aspx
Beside, here are similar posts, you can use as a reference:
https://social.technet.microsoft.com/forums/sharepoint/en-US/1b115343-20e5-4962-af97-793194f07637/metadata-missing-when-revising-document
https://social.technet.microsoft.com/Forums/office/en-US/a65f9828-6e2f-4eb7-bde6-bd0600e3b1a2/migrating-documents-from-moss-2007-to-sharepoint-2010?forum=sharepointadminprevious
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

Similar Messages

HT4889 Am I wrong or does Migration Assistant not work in Mountain Lion (10.8.2) when migrating from a PowerPC running Tiger (10.4.11)? Apple really needs to get on the ball or face losing people buying their new desktop products.

The title alone speaks to my frustration about this issue.
Used the process that was recommended by Apple to migrate from my "Lampshade" iMac (PPC running 10.4.11) to the new iMac (Intel running 10.8.2) and I got bupkiss...
Just a spinning wheel (not beachball) and no drive recognized using Migration Assistant for both nor when using Target Mode on the iMac running 10.4.11 and Migration Assistant on the iMac running 10.8.2. Which is ironic, or more accurately oxymoronic, since the iMac in Target Mode (10.4.11) is recognized on the desktop of the iMac running 10.8.2 but not in the Migration Assistant. And before you can misdiagnose..it is not the Thunderbolt connection since I have the Apple recommended Thunderbolt to Firewire adapter and also used the Firewire 400 to 800 cable to expedite the transfer.
On a personal note...
I'm not bashing Apple for this...they are "head and shoulders" above the competition in what they do but I've been burned a few times so I feel I can share a small bit of loyal customer advice...I understand your iOS and mobile products hold huge sway in company focus and market-share but I find it a tad unwise to slack on the desktop applications. I don't recall any app for the iPhone/iPad family being made on the iPhone/iPad...only from desktop applications if I recall correctly. And how can I clearly "Move my Mac even further ahead" as your marketing states when I can't even migrate my files from my old Mac to my new one in a simple fashion as per your instructions?
I thank anyone in advance with an answer or even a workaround for this issue and please have a great day.

http://support.apple.com/kb/ht4889
Migration from Mac OS X v10.4 Tiger to OS X Lion
Migration from Mac OS X v10.4 computers to OS X Lion over your Wi-Fi or a wired network is not supported. However, if both Macs are equipped with a FireWire port, you can use Target Disk Mode to transfer your data:
Verify that both Macs are equipped with a FireWire port. Note that different model Macs may have different FireWire connectors, which will require an appropriate cable, such as FireWire 400 to FireWire 800.
On the Mac you want to transfer data from, Restart, and immediately hold the T key.
Wait for the FireWire logo to appear on the screen. If it does not, restart and try again.
Connect both Macs via the FireWire cable.
On the Mac you want to transfer data to, Open the Migration Assistant application.
Select the option "From another Mac, PC, Time Machine backup, or other disk" and click Continue.
Select the option "From a Time Machine backup or other disk" and click Continue.
Select your other Mac's volume, such as "Macintosh HD", from the list, and click Cont
EDIT: Actually I realize you did follow these directions and if your drive is seen on the new Mac it should work. You're entitled to free Apple support with the new purchase, I'd give them a call.

-error in XML document- when migrating from BPEL 10.1.3.3 to 10.1.3.4

Hi,
I've just been handed as set of BPEL processes which were developed in 10.1.3.3 and I'm working on migrating them to 10.1.3.4.
Migration of most processes was straight forward, however, there is one process (SendMessage) that accepts an XML document as its input. The message payload is successfully sent in the older version, however, in version 10.1.3.4, I keep on getting the following error.
Server was unable to read request. ---> There is an error in XML document (195, 99). ---> Input string was not in a correct format.
The line number is the end line number of the xml document message.
I've checked both versions and in 10.1.3.3 the ValidateXML option is set to false, whereas in 10.1.3.4 its 'none', which is equivalent to false.
Are there any other settings in 10.1.3.4 that could be causing this error? Has anyone else come across this issue when migrating upgwards from 10.1.3.3?
I would greatly appreciate any suggestions.
Kind regards,
Shiraz

I had recently done the same migration. One of the issues I had faced was while specifying the nillable elements I used to get an error if the namespace definition was in the header. The error was occuring while sending the message to AQ.
I do not know if this will help. Also it would be useful if you could provide details of where the process is failing is it failing at the receive activty or later. What does the process do....
Best of luck with the problem.

Problems with custom authentication when migrating from 3.2 to 4.1.1

Hi,
we’re about to upgrade our APEX instances to 4.1.1 and to migrate our applications. I encountered some problems with our custom authentication schema.
1. Recognize already authenticated sessions: in 3.2 the sentry function could return false as long as the user was not authenticated. Public pages could still be displayed (including the login page). The result of the function apex_custom_auth.is_session_valid returned false until once the sentry function returned true. How can I recognize non authenticated sessions in 4.1.1? I looked for the test the Condition “User is the public user (user has not authenticated)” computes on a page but didn’t found the right one. It’s not what docu states here (comparison with the public user): http://docs.oracle.com/cd/E23903_01/doc/doc.41/e21674/condition001.htm#HTMDB25943. I replaced the test with p_authentication.username = ‘nobody’. It works. But that doesn’t seem to me to be the right way …
2. Post_logout lacks session context: the Post Logout Procedure does not receive a session_id and username. Neither the V(‘APP_SESSION’) nor p_authentication.session_id are set. This applies to both plugin authentication schemes and non-plugin custom authentication schemes. Is there another way to obtain the logged-out sessions infos or is this a bug?
See apex.oracle.com for a demo, workspace WS_MW, gast/gast. Can someone please guide me the way?
Michael

Hello again,
there are no replies until now .... I reviewed some posts regarding custom authentication again and did not find any solution for the issues. Found some that worked with APEX 3.2.1 but not with 4.1.1. I can only work around
1.) in an insecure way, because the non documented (?) user "nobody" can change and all new sessions will be considered authenticated
2.) in a way, that ends up in implementing the logout from the non apex environment outside the authentication schema or authentication plugin.
May be I should contact support for at least the second issue because this doesn't work as documented or am I doing something wrong?
Michael

Custom Auto Attendant Prompts through TUI not working for users who migrated from 2010 to 2013

In Exchange 2010, we started using unified messaging and set up Auto Attendants. We setup a admin role/RBAC for people of a security group to be able to update the message on the auto attendants. They have the UMPrompts assigned role. All of this is working
great in 2010. We have now migrated to 2013, and the users who were migrated from 2010 to 2013 can no longer update the messages through TUI. Newly created 2013 users can and are assigned the EXASCT same permission as the users who have been doing this for
well over a year on 2010. When they call the AA and press #,* they are asked to provide their extension, after doing so the system tells them that extension is not correct. and asks for the extension again. Newly created users with the same permissions
get prompted for their PIN and can log in and change the message just fine.
Confirmed Bug? anybody else having this issue?
What would be different for this process between a user who was migrated from a previous version like 2010 compared to a newer user who has only ever existed on 2013?

What if the migrated 2010 users are in the same DB as the system mailbox? I had a similar issue during a migration; http://www.skypeadmin.com/2014/11/10/known-issue-um-automated-attendant-tui-editing-broken-migration/
Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
SWC Unified Communications
This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

How to use custom forms created in SharePoint 2007 to work in SharePoint 2010

Hi,
We have created some custom forms in SharePoint 2007 (for add a New item and Edit item for some list and libraries) after migration to SP 2010 we found out thet we can use those custom forms because the document versions are 12.0.0.0 which
should be 14.0.0.0 in SharePoint 2010
Could someone please tell me if we can migrate forms from SP2007 to SP2010 as well?
I even tried to change document Version and content but still not working! Do we need to recreate those forms in SP2010?
Thanks
Kate

Hi Khojasteh,
How did you do for changing document version and content?
Whether you tried to set the forms update automatically, then re-publish them.
There are some similar posts for your reference:
Migrate Infopath 2007 to SharePoint 2010 site
Unable to open infopath forms when migrated from MOSS 2007 to sharepoint 2010
Migrate browser based InfoPath Forms with code behind from MOSS 2007 to SharePoint 2013
Plan to upgrade form templates during an upgrade to SharePoint Server 2010
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

SharePoint 2007 Migration SharePoint 2010 Documents Broken Link Issue

Hello All,
I'm in the process of doing a SharePoint migration from 2K7 to 2010 (different platform). In SP 2K7 I have several thousands of documents. I have approx. 5K documents with anywhere from 1 to several links (http, https) that
will break after the migration. Are there any Best Practices to deal with this issue? Any information at all!!!
Thanks
Suge
Deny yourself the knowledge of other cultures, you deny yourself the true riches of the world. Suge

Hi,
There are a lot of resources out there for migrating from MOSS 2007 to SharePoint server 2010. You need to have at least SP2 for MOSS 2007 installed on your WFE server. After that you can check the status of your farm running
stsadm -o preupgradecheck.
I have published a checklist for migration, check it out:
http://social.technet.microsoft.com/wiki/contents/articles/checklist-for-migrating-from-sharepoint-2007-to-sharepoint-2010.aspx
This technet link provide you with a comprehensive guide:
http://technet.microsoft.com/en-us/library/cc303420.aspx
The best approach is to set up a separate SharePoint 2010 farm and the perform a database attach migration. You simply take a backup of your content database and the restore it to your new SQL server, then attach it to a web application you have created.
See the checklist I have provided above.
Regards
Henrik A. Halmstrand
sharepointrevealed.com
getspconfig.codeplex.com
Please click Mark As Answer; if a post solves your problem or
Vote As Helpful; if a post has been useful to you.

Migrate the MOSS application that having custom site defination to SP 2013.

Hi All,
I need to migrate a SharePoint 2007 application that uses the custom site definition in to SP 2013. I believe custom site definition is no more supported in SP 2013. Can anyone please suggest me what should be the approach for migration?
Regards Restless Spirit

Hi Restless,
According to your description, my understanding is that you want to migrate SharePoint 2007 application to SharePoint 2013.
You cannot upgrade directly from the server products in the Office 2007 release to SharePoint 2013. The changes between versions are too great, and the hardware requirements differ so much between versions that a direct upgrade is not possible or supported.
However, you can perform a series of database-attach upgrades to first upgrade your content to SharePoint 2010 Products and then to SharePoint 2013. More information, please refer to
it.
Or, you can use a third party to migrate SharePoint 2007 to SharePoint 2013.
Here are some similar posts for your reference:
http://social.technet.microsoft.com/Forums/sharepoint/en-US/e9542ff4-7812-4e41-9a31-1fe8966c2988/moss-2007-to-sharepoint-2013-migration?forum=sharepointgeneral
http://social.msdn.microsoft.com/Forums/sharepoint/en-US/da49e742-5e38-4b13-9dee-84b2bb4a5cef/migrating-custom-site-definitions-from-moss-2007-to-sharepoint-2010?forum=sharepointdevelopmentprevious
http://sharepointpromag.com/blog/migrating-sharepoint-2007-sharepoint-2013-part-1
http://sharepointpromag.com/blog/migrating-sharepoint-2007-sharepoint-2013-part-2
I hope this helps.
Thanks,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

Cannot Save New Document to SP2010 from Excel 2007

I have two users who cannot save a new file from Excel 2007 to Sharepoint 2010 using the network share path. They receive the following error:
You cannot save the file you selected. The folder you selected is not an actual file system location.
However, other users can save this way with not trouble at all.
When they have the Excel file open, they go to Save As... and the window opens. Then they type in the path to the Sharepoint library where they want to save the file: \\intranet\DavWWWRoot\site\library\
At this point, they should be able to click the Save button and the window will refresh to the Sharepoint library. They would then be able to enter the name of the file and click the Save button again. However, when they click the Save button the first time
to refresh the window, nothing updates and the path they just typed goes away.
My first thought was an issue with permissions, but I've checked and double checked that they are in the correct group.
Then I decided to go even more basic and have them use Windows Explorer to browse to the location. They were able to.
I then had them right click within Windows Explorer, select New, and click Text Document. Not only were they able to create the new text file, but I confirmed it updated
the Sharepoint library successfully. So, that obviously rules out any issues with permissions.
Out of sheer frustration, I even tried mapping a network drive to the Sharepoint library and having them save to the mapped drive location, which of course yielded the exact same error.
I have also double checked that the Webclient service is running on the machines.
One more piece to note is that these two users are still running XP. They'll be upgraded to Win7 later this year, but this needs to work before then.
Any help or suggestions would be greatly appreciated.

Hi,
Did the issue only occur in Excel? What about the other Office suits?
Please copy the site URL to the File name Text Box in the Save as window. Like:
http://intranet\site\library
Regards,
George Zhao
TechNet Community Support

Custom tab missing from Create Site template selection section in SharePoint 2010

Background:I migrated from SP 2007 to SP 2010.
ISSUE: my custom templates are visible in the Gallery list but when i try to create a new site the Custom tab selection is missing.
What am i doing wrong?

Hi,
For a tip to understand for Visual Upgrade refer here :
Visual Upgrade
By Custom Templates, I mean remove old Master Pages : Go To Site Settings --> Look And Feel --> Master Pages (click on Master Pages to open window with Master Pages and CSS Style). From this page select V4Maste.master and default CSS. Refer here for
more on how to change :
Master Page
You can very well get back all your custom settings, but first lets try to resolve your first issue.
Cheers!

Display custom metadata/ add new columns in document explorer of spaces

We have client requirement to show custom metadata in the document explorer home sceen, like Document name, Size, Author, etc..
Can we display metadata from advanced properties of a file like a column or can we add new columns to display to document explorer.
How can we achieve this goal, can we customize taskflow to achieve this goal.
Thank you,

For what it's worth, I posted pretty much the same question a couple of days ago:
How to show document title instead of file name in Document Manager
If you check the source of the task flow you'll notice that the document explorer contains an af:treeTable that iterates over a collection of items.
I have not yet identified the class it is iterating over, but I doubt you will be able to add custom metadata to this table. Perhaps the document title (which I am looking for) which is a common field, but not others.
Might be an enchancement request for Oracle Support.

Custom Metadata View

Is there any way to change the display size of custom metadata labels in the inspector? I have created a bunch of custom metadata labels and given them names that are truncated when displayed in the metadata inspector. When I resize the inspector pane, the value boxes increase in size but the custom label names remain fixed in width (or # of characters). The result is that I can't see the full label. I can't shorten the label names for work flow reasons. Thanks!

I have attached a bunch of optional metadata field presets as a zip file. If you open any one of them in a text editor you can see how they can be modified to match your needs (i.e. line needs to be remarked out using --).
Send me a PEm for info
Edit: the closest to your requirements is named Exif + Image

Unable to create a new folder in document library of SharePoint 2010

Hi There,
Need some help regarding an issue which is occurring after migration from SP 2007 to 2010.
We have recently migrated a site to SP 2010, after migration whenever i tried to create a new folder in a document library it gives me an error message below
SPException: Can not find the form to create default data for the list
Microsoft.SharePoint.Utilities.SPUtility.ThrowSPExceptionWithTraceTag (UInt32 TagId, ULSCat traceCategory, resourceId String, Object [] resourceArgs) 28098007
Microsoft.SharePoint.ApplicationPages.ListFormRedirect.InitializeQueryStringMembers () 1764
Microsoft.SharePoint.ApplicationPages.ListFormRedirect.OnLoad (EventArgs e) +25
System.Web.UI.Control.LoadRecursive () 66
System.Web.UI.Page.ProcessRequestMain (Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) 2428
All the document libraries which are created with the custom list template has this problem.
Moreover, I have verified and found Upload.aspx page is available in Forms folder of a document library.
Can someone help me in resolving this issue.
Thank you in advance.
Vikram
vikram padigala

Hi,
All the document libraries which are created with the custom list template has this problem.
Did you mean you had a custom library template?
Did the issue occur in the library which created use the out of the box template, such as use the Document Library template?
You can check with the OOB template library to test whether they had the same issue.
If the OOB template library works well, the issue may be related to the custom library template.
You can try to recreate a new custom template to check whether it works.
To quickly and accurately find the issue , you can also check the event log and ULS log to see if anything unexpected occurred.
For SharePoint 2010, by default, ULS log is at
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

SharePoint 2010 Slide Library Unable To Select Managed Metadata When Publishing.

Hello,
I'm running into some problems with Managed Metadata when uploading (publishing) slides in a SharePoint 2010 Slide Library. If I have Managed Metadata Site Columns that are set to be required in my slide library, and I publish my slide(s) into the
SharePoint 2010 Slide Library I'm not prompted to enter in my required Metadata before the slide is published. The slide will upload, but then I would need to edit the slide and then enter in the required Metadata.
If I create a new column with a type set to Choice for example, and set it to be required and I upload (publish) a slide I'm now prompted to enter in the required Metadata, but all the Managed Metadata choices are grayed out and I'm unable to select anything.
I'm able to select a Choice for the new column.
Is this a bug within SharePoint 2010 that does not allow me to enter in Required Managed Metadata Tags on uploading (publishing) slides?
Regular document libraries work just fine with required Managed Metadata.
Thanks for any assistance.
v/r
JShidell
v/r JShidell

Hi,
According to your post, my understanding is that the Managed Metadata not prompted to enter value in the required metadata.
I had tested with this issue, and I found the same issue.
We will help to submit the issue to proper pipeline for you.
Again, thank you for your report which will definitely make SharePoint a better products. There might be some time delay.
Appreciate your time and patience.
Thank you for your understanding and support.
Thanks & Regards,
Jason
Jason Guo
TechNet Community Support

Custom DTS package migration from BPC 4.2 ,SQL 2000 to BPC 7.0 M , SQL 2005

Is there any changes required in the custom dts package when migration from BPC 4.2 , sql 2000 Environment to bpc 7.0 , SQL 2005/2008 Environment.
or
Please suggest process for migrating custom dts package from BPC 4.2 ,SQL 2000 Envirnment to BPC 7.0 ,SQL 2005/2008 Environment

When you say "custom dts package" that can mean many different things. What type of customization has been done?
There are a few BPC-related features which changed from 4.2, which must be manually adjusted, if you're using those features.
But SQL itself also changed dramatically in moving from SQL 2000 to 2005. So if your customer's packages are heavily customized around SQL 2000, this may require substantial re-work.
The only migration process for custom DTS packages -- that I'm aware of -- is to use the SQL 2005 migration tool in SSIS, see how much it messed up, and then fix everything else that's still broken.
But there also may be opportunities to improve the package overall. SQL 2005 has a lot of great new features in SSIS, over what was there in SQL 2000.
I haven't started working with SQL 2008 yet, so I can't say what complexity there is in upgrading DTS packages from 2005 to 2008. From what I read in the BPC 7 release notes, it sounds like it's a very minor upgrade, compared to the jump from 2000 to 2005.

Losing out custom metadata info of few documents of a document librarby when migrated from MOSS 2007 to Sharepoint 2010

Similar Messages

Maybe you are looking for