I am migrating MOSS 2007 site to sharepoint 2010 without UI upgrade. In MOSS 2007, to search a specific keyword from the document uploaded on site we use to use "http://sharepointsearchserv.codeplex.com/" tool. The result use to be in xml format. And I would fetch the filename of the document from the xml,Now that I am migrating it to 2010 I require a new tool. Hence I came across this: http://fastforsharepoint.codeplex.com/. But this tool can search only till 10000 records. For next 10000 records it produces below error.
<ResponsePacket xmlns="urn:Microsoft.Search.Response">
<Response domain="">
<Status>ERROR_SERVER</Status>
<DebugErrorMessage>System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]</DebugErrorMessage>
</Response>
</ResponsePacket>"
My query is. Is there any alternate tool which I can use?
I suspect the problem is not with the tool itself, but with the search service.
Check the USL logs to find the cause of the error.
I referred http://www.silver-it.com/node/97 link to solve the issue. But speaking about the tool. When I say "save result" it stops working. And when I click on "save all results" it just saves the code. I want to save the result as xml file. How do i do that?
Related
I am trying to insert the version number stored in SharePoint Online into my Word document - I've done the following thus far:
Activated the Library and Folder Based Retention Site Collection feature
Checked "Enable Labels" in the Information Management Policy Settings for the Document Content Type, and entered "{Version}" into the Label format field
Created a Word document in my library
Opened the document in Word, and inserted a Quick Part (Document Property > Label)
What shows up on the document is {_UIVersionString}, not the actual version number. Not sure what's going on - it seems so close.
In my test, I cannot reproduce your problem.
I can display the correct version number in the document. Below is a screenshot of my test:
This may be caused by the cache, I suggest you to clean up the cache of the SharePoint page and Office first.
You can provide your detailed screenshots, which can help us solve the problem better.
I need to migrate Work Items from one TFS server to another TFS server. I tried migrating them using the TFSMigration tool available in CodePlex.
The problem I am encountering is the schema for the work item on the source TFS is different from the schema of the work item type on destination. I don't want the destination TFS server schema for the work item to be modified. The change in schema is one new column only, but still don't want to take that change.
In one blog it was said that we can do that using Excel but not much details were available. I am not sure we can even use Excel to migrate the entire history related to Excel.
Have a look at the TFS Integration Tools on VS gallery. This supports custom field mappings as part of a migration, documentation here (direct download).
I did this a while back and, not finding an appropriate tool, resorted to copying the title and description etc across manually, as we only had a few active work items at the time, so it only took about an hour.
however, if I need to do it again, I'll use the TFS API to read fields of interest and write them to the new database. that way any schema differences don't matter, and the process is automated but under your control. Search for studying work items with the TFS API for details - it's really very easy.
Of course with both of these approaches (and all the migration tools AFAIK) you will only get a snapshot of the data - all history will be lost (or at best you can query using AsOf to get historical data, but all the entries you make will be timestamped at the moment you write them, not with the historical time that the event originally occurred.)
You can use the Excel editor to edit the source query All Items "Open Query in Microsoft Excel". Then open the destination query All Items "Open Query in Microsoft Excel". Copy and paste the contents from one excel window to the other. Certain fields like attachments will not transfer.
Our company recently upgraded from Sharepoint 2007 to 2010 and with the upgrade it managed to break a filter on one of our sites.
The site is mostly just a dressed up document library with a custom view and has a date filter (by year, month). After the upgrade it randomly generates an error of "Unable to display this Web Part. To troubleshoot the problem, open this Web page in a Microsoft SharePoint Foundation-compatible HTML editor such as Microsoft SharePoint Designer. If the problem persists, contact your Web server administrator." along with a correleation ID. The logs generated on the sharepoint server state "Failed to render field Created_x0020_Date, use default value instead".
The problem does not appear to be with the query or with the returned results until it actually tries to display the web part. Somehow the created date is not getting set? The strange thing is it works intermittently. The web part loads correctly maybe 5% of the time.
Any ideas what could have changed from 2007 to 2010?
Was the "Created_x0020_Date" column a calculated column? Was it modified in any way (such as the current date XSL hack)?
I've seen that sporadic error before and for my problem it was a time-out issue with a poor performing web part pulling from 3 different lists. We increased list throttling, and caching but it didn't help. But if it's just a standard view of the library with no custom XSL in it, then it isn't a code performance issue.
Can't you just create a new created column and copy the old data into the new column using Datasheet view in the browser?
We faced this same error both in a SharePoint 2010 and a SharePoint 2013 enviroment,
when executing an old report.
The cause was the farm XsltTransformTimeOut parameter.
We increased its value (default is 1 second) to 20 (our report lasted 10 seconds to run) and it got ok!
$farm = Get-SPFarm
$farm.XsltTransformTimeOut = 20
$farm.Update()
Hope it helps!
There whatsoever no difference between the Created Date column in SharePoint 2010 and SharePoint 2007.
The differences between the two are mainly new columns. After doing some digging I found this.
You can see the complete reference of the fields here
SharePoint 2010 Document Library Column Reference
SharePoint 2007 Document Library Column Reference
SharePoint 2007 2010 Document Library Column Difference
Now, since we know pretty much nothing of your setup and how this is built we are left to chance a bit. But assuming that guessing a bit is alright I'd say you are either missing the data in the 'Created Date' field which is possible since the field isn't required (check the documents I've linked to). Did you verify that all documents got this value set?
This field (Created Date) use the TimeCreated property to check when the document was created. So if this column isn't filled with data that usually should mean that your documents hasn't been transfered to your new installation but the reference to the document is still there.
http://msdn.microsoft.com/en-us/library/microsoft.sharepoint.spfile.timecreated.aspx
Thats a bit of a chance but thats what I'd start somewhere around that.
Good luck.
I have a method which downloads sharepoint documents to the local disk. I use SPFile.OpenBinary() method to get physical file, but it contains all fields of a parent DocumentLibrary. Does anybody know how to clear file (doc file) from these fields? I found only way to do it using Word interop library (method described here http://maxim-dikhtyaruk.blogspot.com/2009/05/trim-sharepoints-documents.html), but it doesn't fit my requirements cause it works only when Microsoft Office is installed on the machine...
You may want to read this to understand whats going on.
I do not know if this can be turned off or not, but it happens only with Word 2007 documents (docx).
You could do any of the following to turn this off:
Create a new content type and associate it with a document library. Use this document library from now on.
Look into some Open XML library or the Open XML SDK published by Microsoft.
This isn't a bug, it's supposed to be a feature! :-) Seriously though, you need to edit the Word document programmatically to remove these additional fields completely (I think even a content type will leave some behind).
For documents prior to Word 2007, you could use a toolkit like Aspose. I almost needed to do a similar thing once and would have used this product to do it. I'm sure there are other options out there.
For Word 2007 and higher, as SharePoint Newbie says, you should be able to use the Office Open XML formats to edit the document. Here's an MSDN intro article.
So I have a form that uses infopath services via sharepoint, and after multiple attempts at attempting to fix a rendering problem (tables appear WAY too wide to be readable), I think I have found the problem : date controls.
It seems date controls within Infopath 2007 screw with rendering somehow. To test, I made 2 variations of a VERY simple form - one with a date control, one with a text control - and placed them inside a table.
When emailed, the one with the date control rendered incorrectly.
My question is - has anyone experienced this before? If you have time, test it out. I think it is a bug or something, but not exactly sure.
I am using Infopath 2007, Sharepoint 2007, and Outlook 2007.
Updated Sept 19, 2008
Yes, web form capability is checked.
Web compatible date controls? I think so - everything looks perfect in the browser... only the email messes up.
and yes you are correct. My mistake this is Sharepoint 2007. I fixed it above.
If anyone has the time, try it out - it's very frustrating to have to use text boxes for dates. Especially with the 'talent' we have here. lol
Do you have web form compatability checked in all the necessary places? Are you using the web compatible date controls? Are you sure you are using SharePoint 2003, I thought Form Services was a 2007 update.
Could be the same issue I had(or maybe not)...InfoPath cache's the form on the client(seems to check for the form’s unique URN in the cache) which means that if you attempt to click on the email “Edit this task…” the new form is not downloaded, instead the InfoPath form from the cache is displayed.
Run the following on your cmd window to verify this...and post your findings here
"C:\Program Files\Microsoft Office\Office12\INFOPATH.EXE" /cache clearall