Convert RDL to RDLC in vs 2013

Hi I am trying to covert rdl file to rdlc.
rdl created in vs2013(SQL Server 2014) and I am add this also in vs 2013 project.
I rename rdl file to rdlc and place in project.assign data set ,but when run no error occurred but also report will not shown.
but if I add report in project using add new item its working fine .
any idea/possibility why its not working and how I make it working?
I also try https://msdn.microsoft.com/en-us/library/ms252109%28v=vs.80%29.aspx

Hi kuntalb,
As my understanding, you want to add drillthrough action to the second label report, if that is the case, please refer to the following article:
https://technet.microsoft.com/en-us/library/ms159847(v=sql.100).aspx
In addition, since the issue regards SQL Server Reporting Services. I suggest you post the questions in
SQL Server Reporting Services forums. It is appropriate and more experts will assist you.
Regards,
Michelle Li

Similar Messages

Can I convert a 2010 CAB file to 2013 CAB file?

Can I convert a 2010 CAB file to 2013 CAB file?
For further information:
We generate CAB files from MMS Term Store and send it to other teams. Currently we are using 2010 and few consumers are requesting to send a 2013 CAB file. So my question is, can a convert a 2010 CAB file to 2013 CAB file?
Help is appreciated.
Thanks,
Praveen

it seems there is no difference between the cab file that SharePoint 2010 exported, and cab file 2013 exported.
we can export the cab file from 2010, then import to 2013 managed metadata service.
during this step, please make sure the the account you use is added to the relative db 'bulkadmin' permission, then execute following script to import:
$mmsApplication = Get-SPServiceApplication | ? {$_.TypeName -eq "Managed Metadata Service"}
$mmsProxy = Get-SPServiceApplicationProxy | ? {$_.TypeName -eq "Managed Metadata Service Connection"}
Import-SPMetadataWebServicePartitionData $mmsApplication.Id -ServiceProxy $mmsProxy -Path "C:、mmsdata.cab" -OverwriteExisting
Qiao Wei

Converting Word Templates from 2003 to 2013 Version

Hello. I work at a school environment and most of our secretaries had been running Office 2003. They have a lot of Word templates. Recently, as we have decided to upgrade Office to 2013, we have the problem of hundreds of old templates
that need to be converted over to the 2013 version.
Is there a quick and efficient way to do this? Instead of manual converting each file, one by one.
Thanks in advance!

In addition to the answer of Edward I would add the following line of code:
Sub Convert2003To2013()
' Convert2003To2013 Macro
Application.ScreenUpdating = False
Dim strFolder As String, strFile As String, wdDoc As Document
strFolder = "D:\Sample\OfficeDev\Word\OldFolder"
If strFolder = "" Then Exit Sub
strFile = Dir(strFolder & "\*.doc", vbNormal)
While strFile <> ""
If InStrRev(strFile, ".docx") = 0 Then
Set wdDoc = Documents.Open(FileName:=strFolder & "\" & strFile, _
AddToRecentFiles:=False, Visible:=False)
wdDoc.Convert
wdDoc.SaveAs2 FileName:=strFolder & "\" & Left(strFile, InStrRev(strFile, ".doc")) & "docx", _
Fileformat:=wdFormatXMLDocument, AddToRecentFiles:=False
wdDoc.Close SaveChanges:=False
End If
strFile = Dir()
Wend
Set wdDoc = Nothing
Application.ScreenUpdating = True
End Sub
I added the wdDoc.Convert because otherwise you are not explicitly converting documents but only renaming them to .docx
The additional functionality of Office 2013 comes available when the document is actually converted. You can test this by opening the document after het has been really converted, you should be able to see the SmartArt options. If you only rename them to
.docx you will see that the 'new' smart art functionality is not available.
Doesn't mean that the provided code block by Edward doesn't work, it does a great job. My advice would be to add the convert line if you really want 'converted' files.
Last thing you have to think about is these code snippets use SaveAs2, that means that you will get two instances of your document. If you choose convert you are actually converting the original document. In that case you do not choose SaveAs2
but you use Save.
Maurice
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer. Thank You

Converting from InMotion Hosting to Exchange 2013 Migration

Hello everyone,
We are looking to convert our current mail service being hosted on InMotion using POP3 to our Exchange 2013 server. Is there a migration guide somewhere I could find or something to lead me in the right direction? We want to forward the mail from InMotion
to the Exchange mailboxes as well. I know this involves converting MX records and the such but I feel like something is missing in the grand scheme of things.

Hi,
The migration can include:
1. Account migration.
2. Database migration.
3. Some A and MX records need to be configured.
For more details, you can either consult Inmotion support or Microsoft support below:
Inmotion Support
https://www.inmotionhosting.com/support/launch-chat/?rdid=2324923566971164486&url=http%3A//www.inmotionhosting.com/support/email/general-information/getting-started-guide-email
Microsoft Advisory Support
https://support.microsoft.com/gp/advisoryservice
Thanks,
Simon Wu
TechNet Community Support

Xi Pro wont convert all sheets of an Excel 2013 to pdf

When using the "combine files in Acrobat" only sheet #1 of the spread sheet is converted. However, this only happens on our machine that has Excel 2013. The same documents are converted flawlessly when the feature is used on a machine that has Excel 2010.

Hi,
Kindly post your query in Adobe Acrobat forum:Acrobat
Regards,
Florence

Convert LabV 5.1 *.llb to 2013

Can somone please upconvert this LabV 5.1 llb to 2013? Thanks...
Solved!
Go to Solution.
Attachments:
Financial front panel.llb ‏671 KB

Mass compiled in 8.2.1, which you can open with 2013.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
Financial front panel.llb ‏464 KB

Drill Down Report - On Drill Click, Tablix Expands to right.

Hi All
I created an RDL File(Drill Down) in SSRS and consumed the same in aspx page, changing its extension to rdlc. Drill Down is working well in local. But When it is hosted in server, On drill Click tablix expands to right.
Awaiting for the response.
Thanks

Hi Madhava_Reddy,
I have tested on my local environment and can't reproduce the issue, this issue can be caused by many factors, it can be caused by the way you have converted the RDL file the RDLC file and can be also caused by the browser type and version you are using.
Please reference to the details information below to make sure you have do the correct action and provide us more information:
Please reference to the article below to make sure you have convert the rdl file to rdlc file correctly:
Converting RDL and RDLC Files
What is the type and version of browser you are using? Not all browsers support all report functionality.
Planning for Reporting Services and Power View Browser Support (SSRS 2012)
(This article describes the support and requirements for Report Manager management features, viewing reports, the Report Viewer controls in Visual Studio)
Please try to follow the article in step1 to convert the rdl to rdlc file one more time and try to run the application on other type of browser to have a check. You can also try to create an rdlc report in the application to have check
if the report viewer controls will display the drilldown action correctly.
What do you mean drilldown report (.rdlc) works fine in local but not in server?
If your problem still exists, please try to provide snapshot of the unexpected result.
Regards,
Vicky Liu
Vicky Liu
TechNet Community Support

How do you convert OPC servers 2012 opf file to OPC servers 2013?

When I upgraded from LV 2012 to LV 2013 SP1 my NI OPC Servers 2012 was also involuntarily upgraded to 2013. Now my shared variables don't work. How do you migrate or convert a 2012 *.opf file to 2013? The only clue given by the software Help file is a hint that ProgID Redirect can be used, but there is no explantion of how or where to find this feature or how to use it!

Hi JT1958,
I set up a system that had LabVIEW 2012 along with NI OPC Servers 2012 and upgraded it to 2013. I found that the .opf file I created from NI OPC Servers 2012 was able to be opened by NI OPC Servers 2013 without any issues and I was able to access the tags from a LabVIEW project. However, one difference between our setups is that I did not upgrade my project from LabVIEW 2012 to 2013 - I create a new project in LabVIEW 2013.
Are you getting any error message when you try to open the .opf file in NI OPC Servers 2013? Or did it seem to import correctly? What if you try to create new bindings for a few shared variables rather than using your existing shared variables (just to see if it works)? Perhaps some of the references just need to be updated.
Hope this helps!
Best Regards,
Matthew B.
Applications Engineer
National Instruments

How to Export Import vCard contacts in Outlook 2013? Does it convert multiple Contacts at once?

I am using latest edition of Microsoft Outlook 2013. I believed that it will definitely help to convert 1500 vCards contacts into Outlook 2013, all at once, but it is not supported to be possible because, still, Outlook 2013 has not improved in this direction.
Any hope for me rather than exporting or importing contacts one by one???

If it is one time requirement, simply use vbacode but it exports few garbage values. I tried this code and got below given garbage value (in place of image) apart from real one in every vCards. Vbacode did not export images:
X-MS-CARDPICTURE;TYPE=JPEG;ENCODING=BASE64:
/9j/4AAQSkZJRgABAQEAYABgAAD/2wBDAAYEBQYFBAYGBQYHBwYIChAKCgkJChQODwwQFxQY
GBcUFhYaHSUfGhsjHBYWICwgIyYnKSopGR8tMC0oMCUoKSj/2wBDAQcHBwoIChMKChMoGhYa
KCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCgoKCj/wAAR
CACUACcDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QAtRAA
AgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFDKBkaEII0KxwRVS0fAkM2JyggkK
FhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWmNkZWZnaGlqc3R1dnd4eXqDhIWG
h4iJipKTlJWWl5iZmqKjpKWmp6ipqrKztLW2t7i5usLDxMXGx8jJytLT1NXW19jZ2uHi4+Tl
5ufo6erx8vP09fb3+Pn6/8QAHwEAAwEBAQEBAQEBAQAAAAAAAAECAwQFBgcICQoL/8QAtREA
AgECBAQDBAcFBAQAAQJ3AAECAxEEBSExBhJBUQdhcRMiMoEIFEKRobHBCSMzUvAVYnLRChYk
NOEl8RcYGRomJygpKjU2Nzg5OkNERUZHSElKU1RVVldYWVpjZGVmZ2hpanN0dXZ3eHl6goOE
hYaHiImKkpOUlZaXmJmaoqOkpaanqKmqsrO0tba3uLm6wsPExcbHyMnK0tPU1dbX2Nna4uPk
5ebn6Onq8vP09fb3+Pn6/9oADAMBAAIRAxEAPwD6UdwpAPU0oIwSTxVeQ7nOPoKRj2B4FAEk
k4/g59zREMgk9fWoFGSKsr8qc+maAIJPnmx6cUUkIy5aigBw4yfSkpT93680lABEMtUs52xk
evFJAOabcHkLQA1DsiJ70US8Kq0UAK3Xim0vagdfpQBYhHy5qufmm/GrJ+SP6Cq0PLE0AJMc
vj0opjNlyfeigCTtTohyKb2qaEfyxQAlw2EA9ajT5YyfWluDlwPQUFSVCryeM0AV6KmEaLy5
59KKAFHJxU0ZwoxyTzSBoz0Xn6UOSqEjigBDGN2X5J7CmSSEYCjbSRZLEnkgUyQgufSgBEG5
vmNFNAycCigCzEPmH50s56D8adEvyk/hTJGXeeMkcc9BQAkQIXPvUeFX7xyfQVK5Pl4OBwBx
UFAAXPRcKPaimUUAaJ4TJ7VUA3MPerMxxGfeoI+pPoKACY8Adjk1FT5fv49OKZQAyiiigC3c
HkD0psXC89zSSHLNTjwn0H86AISckmkoPWigBlFFFAFoPuIBHWnOVI5xzTI+pPoKSTqB6CgA
2Ken6GmGP3/MU09aAxHQkUABRscc/Q0Ubz3AP4UUATp9xvwpj/fb60UUARnrRRRQAyiiigD/
2Q==
X-MS-OL-DESIGN;CHARSET=utf-8:<card xmlns="http://schemas.microsoft.com/office/outlook/12/electronicbusinesscards" ver="1.0" layout="left" bgcolor="ffffff"><img xmlns="" align="fit" area="16" use="cardpicture"/><fld xmlns="" prop="name" align="left"
dir="ltr" style="b" color="000000" size="10"/><fld xmlns="" prop="org" align="left" dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="telwork" align="left" dir="ltr" color="000000" size="8"><label
align="right" color="626262">Work</label></fld><fld xmlns="" prop="telcell" align="left" dir="ltr" color="000000" size="8"><label align="right" color="626262">Mobile</label></fld><fld xmlns="" prop="email" align="left"
dir="ltr" color="000000" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld
xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/><fld xmlns="" prop="blank" size="8"/></card>
REV:20130313T094717Z
END:VCARD
As my no of vcards were limited, so i removed this value manually from all and missed my vcard avatar.
If your requirement is on regular basis or permanent and vcards have profile images then simply call to vCard magic application that seems pretty good.

Please Convert Vis from Labview 2013 to Labview 2011

Please convert the attached Vis from Labview 2013 to Labview 2011
Solved!
Go to Solution.
Attachments:
Convert from2013 to 2011.zip ‏255 KB

Here you go.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Attachments:
Converted to 2011.zip ‏176 KB

How to make SharePoint 2013 convert License type in PowerShell?

How create script for passing Product Key for converting farm license type for Sharepoint 2013 like it is describied below:
http://macslui.blogspot.com/2013/02/sharepoint-2010-convert-license-type.html

How create script for passing Product Key for converting farm license type for Sharepoint 2013 like it is describied below:
http://macslui.blogspot.com/2013/02/sharepoint-2010-convert-license-type.html
All of the methods for licensing are marked internal, so without reflection you wouldn't be able to set the license via PowerShell.
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

What is best practice to convert a SP2010 Solution to a SP2013 Solution

Hi,
i have developed a Solution for SharePoint 2010 which includes some WebParts, some Custom Application Pages and a TimerJob.
I would like to convert this Solution to a SharePoint 2013 Solution.
What is the preferred way to do this?
Best Regards
Bog
Developers Field Notes | www.bog1.de

Check below article which explains in details about converting SharePoint 2010 solutions and projects to SharePoint 2013
http://zimmergren.net/technical/upgrading-your-sharepoint-2010-visual-studio-projects-and-solutions-to-sharepoint-2013
if you have multiple projects which need to be migrated you can use the below powershell script
http://www.codeproject.com/Articles/522220/ConvertingplusmultipleplusSharePointplus2010pluspr
My Blog- http://www.sharepoint-journey.com|
If a post answers your question, please click Mark As Answer on that post and Vote as Helpful

How do I enforce "Show My Picture" instead of "Hide My Picture" in Lync Server 2013?

I was scouring TechNet and the web for a script that could perform the same task as one that I previously used for Lync 2010.
In Lync 2010, we had already used Lync policy to enforce that only the Active Directory photo could be used. One thing that we couldn't set via policy however was the ability to complete remove the "Hide My Picture" option in Lync 2010 client.
This left users with the ability to freely switch between showing the Corporate photo or no photo. I did eventually find and make use of script that constantly checked for this setting switch, then switched all users back to the desired "Show My Picture"
setting. I don't recall who wrote it, but it's easy to find on technet. As we started to move more and more users to our Lync 2013 enterprise pool, I noted that even though the script was running, the setting seemed to be changeable. A closer look revealed
that the script didn't function correctly against SQL for our 2013 pool.
I took the concept and applied it to Lync Server 2013 after studying the differences in Userdata. In Lync 2013, because UserData is in .zip, you need to convert it to 2010 format XML to use logic intended for Lync 2010. My script will extract 2013 data,
convert it to 2010, query for users who are set to "Hide My Picture" and then export any guilty users to an edited2010 XML. The script then converts this to 2013 Format .zip, and uploads the data for these users only. I chose to use Update-CSUserData
insted of Import-CSUserData as this avoids having to restart my Front End. I then use a scheduled task on my Front End server which runs this script every hour.
Please note: You can use this script, but I guarantee nothing about it's functionality, and I am not responsible for how you positively/negatively use it. You should always test things in a Lab Environment. Furthermore, this script was run on a relatively
smaller Enterprise system in which we are by default set to "Show My Picture" and already assigned as part of our user policy the ForceADPhoto attribute. This means that running the script is less intensive on my FE than say on a FE with 10,000 users
where none of the users were set to "Show My Picture". Please keep this in mind when planning to execute against your FE. You may want to edit my script and insert the -UserFilter or -WhatIf in the Export-CsUserData UpDate-CsUserData.
Anyways, I hope this solves the similar issue for many of you Lync 2013 administrators. Please feel free to share my work with others if it does, and also give this post some good feedback and/or mark my post as the answer to your problem.
Alas, here's the script (save it as a .ps1 , i.e. ForceShowMyPicture.ps1)
#Lync 2013 ForceShowMyPicture - Compiled by Octavio A. Serpa (Octavio-Admin on TechNet)
# Import Lync Module
Import-Module “C:\Program Files\Common Files\Microsoft Lync Server 2013\Modules\Lync\Lync.psd1"
###Variables To Set
#This variable is a folder where files will be temporarily written
$folderPath = “C:\Lync2013Scripts\Export”
#This is the FQDN of the pool in which the users you want to target reside
$poolFQDN = “<lyncpool.domain.local>”
###Done
#Message Out
Write-Host -ForegroundColor YELLOW “CHECKING THAT TEMP EXPORT FOLDER PATH EXISTS"
If (-not (Test-Path "$folderPath" -pathType container))
"ERROR: Your Export Directory doesn't exist!"
Exit
Write-Host -ForegroundColor Green “TEMP EXPORT FOLDER DOES EXIST"
Write-Host -ForegroundColor YELLOW “PRE-CLEANING OLD EXPORT/IMPORT FILES"
If (Test-Path "$folderPath\Lync2013UserData.zip") { Remove-Item "$folderPath\Lync2013UserData.zip" }
If (Test-Path "$folderPath\Lync2010UserData.xml") { Remove-Item "$folderPath\Lync2010UserData.xml" }
If (Test-Path "$folderPath\Lync2010EditedUserData.xml") { Remove-Item "$folderPath\Lync2010EditedUserData.xml" }
If (Test-Path "$folderPath\Lync2013EditedUserData.zip") { Remove-Item "$folderPath\Lync2013EditedUserData.zip" }
Write-Host -ForegroundColor Green “PRE-CLEANING COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “EXPORTING LYNC 2013 POOL USER DATA”
Export-CsUserData -PoolFqdn $poolFQDN -FileName $folderPath\Lync2013UserData.zip
Write-Host -ForegroundColor Green “EXPORT COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “CONVERTING LYNC 2013 USER DATA TO 2010 FORMAT”
Convert-CsUserData -InputFile "$folderPath\Lync2013UserData.Zip" -OutputFile "$folderPath\Lync2010UserData.xml" -TargetVersion Lync2010
Write-Host -ForegroundColor Green “CONVERSION COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “CHECKING THAT FORMAT CONVERSION WAS SUCCESSFUL AND .XML EXISTS”
If (-not (Test-Path "$folderPath\Lync2010UserData.xml" -pathType leaf))
"ERROR: Verify that $folderPath is writable!"
Exit
Write-Host -ForegroundColor Green “CONVERSION COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “LOADING XML”
$d = [xml] (Get-Content "$folderPath\Lync2010UserData.xml")
Write-Host -ForegroundColor Green “XML LOADING COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “CORRECTING AD PHOTO SETTING”
$changes = 0
$lastProcessedUser = $null
foreach ($hr in $d.HomedResources.HomedResource)
$found = 0
foreach ($c in $hr.Containers.Container)
  foreach ($p in $c.Publication)
   If ($p.CategoryName -eq 'contactCard' -and $p.InstanceNum -eq 6 -and $p.Data.contactCard.displayADPhoto -eq 'false')
    If ($hr.UserAtHost -ne $lastProcessedUser)
     "$($hr.UserAtHost) reset"
     $lastProcessedUser = $hr.UserAtHost
    $p.Data.contactCard.displayADPhoto = 'true'
    $p.Version = (([int] $p.Version) + 1).ToString()
    $p.PrevPubTime = $p.LastPubTime
    $p.LastPubTime = (Get-Date -Format s).ToString()
    $found = 1
    $changes++
If ($found -eq 0) { [Void]$d.HomedResources.RemoveChild($hr) }
Write-Host -ForegroundColor Green “AD PHOTO SETTING CORRECTIONS COMPLETED SUCCESSFULLY"
#Message Out
Write-Host -ForegroundColor YELLOW “Changes: $changes"
If ($changes -ne 0)
#Message Out
Write-Host -ForegroundColor YELLOW “RE-SAVING XML”
$d.Save("$folderPath\Lync2010EditedUserData.xml")
#Message Out
Write-Host -ForegroundColor YELLOW “CONVERTING LYNC 2010 .XML BACK TO 2013 .ZIP FORMAT"
Convert-CsUserData -InputFile "$folderPath\Lync2010EditedUserData.xml" -OutputFile "$folderPath\Lync2013EditedUserData.zip" -TargetVersion Current
#Message Out
Write-Host -ForegroundColor Green “CONVERSION BACK TO 2013 .ZIP FORMAT SUCCESSFUL"
#Message Out
Write-Host -ForegroundColor YELLOW “IMPORTING LYNC 2013 POOL DATA FOR CORRECTED USERS”
Update-CsUserData -FileName $folderPath\Lync2013EditedUserData.zip -Confirm:$false -Verbose
Write-Host -ForegroundColor Green “IMPORT COMPLETED SUCCESSFULLY"
Write-Host -ForegroundColor YELLOW “STARTING POST-IMPORT-CLEANUP OF EXPORT/IMPORT FILES"
If (Test-Path "$folderPath\Lync2013UserData.zip") { Remove-Item "$folderPath\Lync2013UserData.zip" }
If (Test-Path "$folderPath\Lync2010UserData.xml") { Remove-Item "$folderPath\Lync2010UserData.xml" }
If (Test-Path "$folderPath\Lync2010EditedUserData.xml") { Remove-Item "$folderPath\Lync2010EditedUserData.xml" }
If (Test-Path "$folderPath\Lync2013EditedUserData.zip") { Remove-Item "$folderPath\Lync2013EditedUserData.zip" }
Write-Host -ForegroundColor Green “POST-IMPORT-CLEANUP COMPLETED"
#Message Out
Write-Host -ForegroundColor Green “AD PHOTO SETTING SUCCESSFULLY UPDATED"

When I try to run this I get the follow error. Any thoughts?
Update-CsUserData : Unable to cast COM object of type 'System.__ComObject' to interface type
'Microsoft.Rtc.Interop.User.ICsUserManagement'. This operation failed because the QueryInterface call on
the COM component for the interface with IID '{D5ADD966-BDC3-4A8F-BFE8-6A59A9F74CB2}' failed due to the
following error: Class not registered (Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
At C:\Lync2013Scripts\ForceDisplayPhoto.ps1:113 char:1
+ Update-CsUserData -FileName $folderPath\Lync2013EditedUserData.zip -Confirm:$fal ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: ([email protected]:String) [Update-CsUserData], Invalid
   CastException
    + FullyQualifiedErrorId : Microsoft.Rtc.Management.AD.Cmdlets.ImportOcsUserDataCmdlet

Word 2013 crashing opening Microsoft Word 97-2003 Document

Hi
I am having a major problem with a large number of Word docs which have been copied to my file server. The docs are in Microsoft Word 97 – 2003 format and open fine with Office 2007. I recently rolled out Office 2013 to a department. When they try and open
these docs by double clicking the file, the Word splash screen with status "Starting..." opens with animated dots but stays in this state. I have left this for over 10 minutes but it doesn’t open. I end up having to close the splash screen using
the top right corner cross but if I check in task manager the task remains eating up 25-30% of the CPU - I have to kill the task from here. I have tested this locally and in RDS where majority of users work from hosted office sessions and the problem is evident
in both. The major problem is that RDS server CPU can reach 100% if a couple of users run into the problem.
Going back to the issue. If I open up a blank instance of Word 2013 first and go File - Open and browse to the file, if I choose “Open and Repair” the file opens with “Errors detected”:
"Drawn Objects and Text Boxes 1"
If I select "go to" it goes to the Footer/headers - There is nothing in the header/footer that looks like it is causing an issue. If I now save the file either as 2003 or docx and close, the next time I try and open (double click) the file opens
in compatibility mode or normal mode no problem. It seems strange Word is not able to automatically open/detect and repair anything it doesn’t like.
Does anyone have any suggestions on how I can work around this?
Thanks

Hi,
Does this happen to all 97-2003 Word files?
Word 2013 now has lots of updates compared with earlier version of Word, lots of features have been updated. Use Word 2013 to open documents created in earlier versions of Word (Word 97-2003 format), you will probably encounter unexpected problems,
expecially for those heavily formatted files.
We would suggest you to convert your document to the Word 2013 file format, then you will be able to access the new and enhanced features in Word 2013.
Regards,
Ethan Hua
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Requesting .llb with 14 .vi's from 5.1 to 2013

Hello again, I am delighted how active and helpful this community is. I am requesting a library containting 14 .vi's made in labview 5.1 to be converted to be compatable with labview 2013. The library of interest is attached. Cheers.
Solved!
Go to Solution.
Attachments:
KE6485 Examples.llb ‏795 KB

Hi,
Here it is in LV 8 You can read this in LV 2013
Kees
Attachments:
Mass Compile.zip ‏232 KB

Convert RDL to RDLC in vs 2013

Similar Messages

Maybe you are looking for