Getting started with OMPM 2010
Still using OMPM? Give Office Telemetry Dashboard a try!
___________________________________________________________
To celebrate the release of the Office Migration Planning Manager (OMPM) for Office 2010, I will be creating a series of blog posts that describe OMPM installation, basic and advanced usage, Q&A, and any other topics that come up. Do you have OMPM (or Office Environment Assessment Tool [OEAT]) questions that you’d like to see answered in this blog? Please leave your ideas in the Comments of this blog post for future consideration.
For this first post, I’ll walk you through a basic installation of OMPM using SQL Express 2008 R2 as the database back end. I’ll also scan my laptop to assess my old Office files and go over some of the initial scan results.
Let’s get started!
1. For this walk-through, I will be using the Access reporting tool to view the OMPM scan data. Therefore, make sure that you have Access 2007 or later installed on the computer where you install OMPM.
2. Download and install OMPM from the Download Center. The download process extracts the OMPM files to a folder of your choice. I will be using C:\OMPM for this walk-through.
3. Install SQL Server 2008 R2 SP2 - Express Edition. You can choose either the 32-bit or 64-bit edition. Remember which edition you install so that you can choose the same edition for the components you install in Steps 5 and 6.
4. The setup process for SQL Server 2008 R2 SP2 Express takes a while to download and extract files. Accept the various prompts and wait for the opening page of SQL Express 2008 R2, called the SQL Server Installation Center, to appear after extraction is complete. Then, follow these steps:
a. In the SQL Server Installation Center, click New installation or add features to an existing installation.
b. In the SQL Server 2008 R2 Setup wizard, read the license terms and accept them, and then click Next.
c. On the Feature Selection page, accept the defaults (all checkboxes selected). Click Next.
d. On the Instance Configuration page, create a named instance called OMPM. Click Next.
e. On the Server Configuration page, accept default service accounts. Click Next.
f. On the Database Engine Configuration page, accept the default authentication mode (Windows authentication mode). Your user account will be shown as a SQL Server administrator. Click Next.
g. On the Error Reporting page, click the check box if you want to send error reports to Microsoft. Otherwise, just click Next.
h. Wait for the installation process to finish, and then close the wizard and the SQL Server Installation Center.
5. Install the 2005 Backward Compatibility Pack from the December 2008 Feature Pack for Microsoft SQL Server 2005. (Select the SQLServer2005_BC package from the long list of downloads according to the correct bitness, either SQLServer2005_BC.msi or SQLServer2005_BC_x64.msi). Accept the defaults for all options.
6. Install the Microsoft SQLXML 4.0 SP1 pack. Accept the defaults for all options.
Now that you have the SQL components installed, you are ready to create a database for storing OMPM results. Take the following steps:
1. In an Administrator command prompt window, navigate to the folder where you installed OMPM, and then open the Database folder.
2. Type the following command to create a database called ompmdb for the ompm SQL instance:
createdb.bat .\ompm ompmdb
When you execute the command successfully, you will see the following results in the command prompt window:
C:\OMPM\Database>createdb.bat .\ompm ompmdb
Microsoft Office Migration Planning Manager version 2.0
Database Provisioning Tool
Copyright (c) 2010 Microsoft Corporation. All Rights Reserved.
Database 'ompmdb' was created successfully.
If you are running the command prompt without administrator privileges, the command will fail.
You are now ready to configure OMPM settings in the Offscan.ini file, which is located in the Scan folder where you installed OMPM. Navigate to the Scan folder and double-click Offscan.ini to edit it. I’m only going to change a handful of settings for this walk-through, but I will also point out some new settings in case you want to experiment. You can find more information about each setting in Offscan.ini in the OMPM Technical Reference.
Note: If you have permissions issues when trying to save Offscan.ini, add yourself to the permissions list for the OMPM folder and let me know via this blog if you encounter this issue.
The table below shows various parameters in Offscan.ini that I will use in this walk-through. Any parameter in bold indicates that I’ve changed the default.
[Run] ;Run ID is a unique ID for this distribution of the scan.
RunID=1001
|
Each time you run a scan, you must increment this number, otherwise the scan won’t start. When you view your OMPM scan results by using the Access report viewer, you can view all runs or a selected run.
|
;Description can be used to describe any extra info about the Run. I.E. Month/Year
Description="ORK team blog OMPM scan."
|
The description also appears in the OMPM Access report viewer. I highly recommend that you use a unique description for each run. |
[Scan] ;SkipOldAccessedFiles: if set to 1, offscan will skip files with a Last Accessed Date less than OldAccessedDate ;if set to 0, offscan will not skip old files based on Last Accessed Date
SkipOldAccessedFiles=0
;OldAccessedDate: files with a Last Accessed Date before OldAccessedDate will be skipped if SkipOldAccessedFiles=1. ; Date format should be “YYYY/MM/DD”
OldAccessedDate=2005/01/01
;SkipOldModifiedFiles: if set to 1, offscan will skip files with a Modified Date less than OldModifiedDate ;if set to 0, offscan will not skip old files based on Modified Date
SkipOldModifiedFiles =0
;OldModifiedDate: files with a Last Modified Date before OldModifiedDate will be skipped if SkipOldModifiedFiles=1. ;Date format should be “YYYY/MM/DD”
OldModifiedDate =2005/01/01
|
OMPM 2010 now offers a way to limit scanning to only files that have been modified or accessed within a specified date period. These settings are not enabled by default, but we recommend enabling them to keep the scan results manageable. Work with your business groups to determine if scanning every old file is necessary, or if you can limit the scan (and eventual conversion) to files that have been accessed or modified after a specified date.
For this walk-through, I’m not going to skip files by accessed or modified date because I want to ensure that I get a variety of scan results. |
;ScanMacros: if set to 1, offscan will attempt to scan macros in scanned filetypes for API or Object Model compatibility issues. ;if set to 0, offscan will not attempt to scan macros for API or Object Model issues
ScanMacros=1
|
ScanMacros is another new setting for OMPM 2010. For this walk-through, I’m going to enable macro scanning (the default is 0-disabled). |
;ScanMacrosX64:if set to 1, offscan will attempt to scan macros in scanned filetypes for x64 compatibility issues ; if set to 0, offscan will not attempt to scan macros for x64 compatibility issues
ScanMacrosX64=1
|
ScanMacrosX64 is another new setting for OMPM 2010. For this walk-through, I’m going to enable X64 macro scanning (the default is 0-disabled). |
FoldersToScan] ;Folder=C:\ ;Folder=\\server\share
Folder=\\jillT400\C$
|
I’m going to scan my remote laptop’s C drive. You can specify multiple clients to scan here. |
After you’ve completed and saved your offscan.ini edits, it’s time to execute a scan.
1. In an Administrator command prompt window, navigate to the Scan folder and type the following command:
offscan.exe
2. You can watch the progress as each file is scanned. Most files are scanned quickly, but some can take a few seconds to complete. When the scan is complete, you’ll see the final lines of output, which are similar to this:
Start: 2010-08-04 12:33:59
End: 2010-08-04 13:01:18
Seconds: 2068
Total number of files scanned: 133770
Total number xml logs created: 5253
Scan Complete
After the scan completes, your next step is to import the scan into the SQL database.
1. At an Administrator command prompt window, navigate to the Database folder, and then type the following command:
ImportScans.bat .\ompm ompmdb c:\ompm\scandata
2. Wait while the scan data is imported into the SQL database.
Now you are ready to use the OMPM Access Report Viewer. Follow these steps:
1. Navigate to the c:\ompm\report folder and double-click the ompm.accdr file. (Update: A new version of ompm.accdr is available here.)
2. In the Microsoft Access Security Notice dialog box, click Open.
3.On the Welcome to the Office Migration Planning Manager screen, enter the following information:
Server: .\ompm
Database: ompmdb
4.Click Connect. You’ll see new links appear at the bottom of the page, like this:
5. Click Office 2010 Compatibility, which takes you to the Overview tab of the report viewer:
6. Click the Issue Summary tab to view a summary of the scan results. Depending on your scan results, you’ll see issues that are classified as Green, Red, and Yellow.
7. Now let’s view the Scanned files tab to take a closer look at the red and yellow issues.
8. Click the DOWN ARROW next to the Max Level column to filter the list to show only red and yellow issues. (FYI, if you don’t have any Red issues, they won’t appear in this list.)
9. In the filtered list, click the file name link to view more details about the issues detected during the scan. Here is one example of a PowerPoint file that has both red and yellow issues:
I’ll wrap up this first blog post here to give you time to experiment on your own. For my next post, I’ll review the results from macro scanning.
Comments
- Anonymous
January 01, 2003
I've run into the same issue as others where the Import function just hangs and never completes. I've found 2 ways around this issue:
- Extract all of the XML files out of the CAB files and then point my import at the folder containing the extracted files. Once you do that, they should import, but it will take about 10x as long as the import process using the CAB files.
- Setup a clean Windows 7 (x86) virtual machine with Office 2010 (x86) and did the OMPM setup on it and then copied all of the SCANDATA files over to it and ran the import. Worked fine even though it was hanging on my main system but worked fine in the VM. Not really sure what the original issue was, but don't care at this point as it's working and I'm able to get the data. Also in case you missed it in the docs, you need Access 32-bit for running the reports. Won't work using a 64-bit install of Office so that was more fun.... I scanned one share with over 435,000 files and 350,000 files failed with the "File Type Not Supported by OMPM Deep Scanner." error but I'm suspecting that many of these are from Office 95 which is unsupported by the tool. The tool should include more information here about WHY it's not supported (maybe include what the file type/version is in the report instead of simply that it's not supported?). Hope some of this is helpful.
Anonymous
January 01, 2003
bala, I heard from someone who saw the same errors in scanning Access files and he came up with the following workarounds: To work around this issue, I had to modify the configuration file (offscan.ini): MaxCopyFileSize=300 If you set this parameter to 300 you will get a new error : “timeout error”. In that case, you have to modify the values of the parameters RetryCount & RetryInterval [Network] RetryCount=15 ;set this to the number of reties per file you would like before moving on RetryInterval=1500 ;set this to the number of milliseconds to wait between retries. Side effect: OMPM will be very slow.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
alistg, we believe this may be an error with your proxy server. I have responded to your question in the TechNet Forums.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
xcj, please contact us at feedork@microsoft.com for assistance with the issue you describe.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
We scanned a larger number of files (about 1.5 mill). While importing the scans we get an error: CRITICAL ERROR: The mapping phase of import unexpectedly failed. Your database may be in an unstable or corrupt state. and our reports are empty, no data. Do you have an idea, what is happening? Thanks a lot, HeinzAnonymous
January 01, 2003
Erik, here is a suggested workaround from one of our program managers. He included a screenshot but I can't put it in the comments, so please let me know your email address and I can send it if this explanation needs the accompanying graphic: I have got myself into this issue once before by aborting a scan. The cmd you referenced should have fixed this. I suggest you look at the OMPM DB table “Process_Control” and verify the importinprogress is really set to zero. You can use your choice of SQL browsers or cmd lines to check this out. It should look something like this: <screenshot> If you are just getting started, the “easy” fix is to simply delete the database with the provided deletedb.bat and then re-create the db.Anonymous
January 01, 2003
Daniel, someone else left a similar comment with the same error back in 2011. Did you happen to see it? I'll repost the response here: "I have got myself into this issue once before by aborting a scan. The cmd you referenced should have fixed this. I suggest you look at the OMPM DB table “Process_Control” and verify the importinprogress is really set to zero. You can use your choice of SQL browsers or cmd lines to check this out. It should look something like this: <screenshot>. If you are just getting started, the “easy” fix is to simply delete the database with the provided deletedb.bat and then re-create the db." You say you've already tried deleting and recreating the database and that didn't help. If the above advice is not useful, you could also try restarting the SQL server. You could also try our new compatiblity tool called Telemetry Dashboard. blogs.technet.com/.../still-using-ompm-give-office-telemetry-dashboard-a-try.aspxAnonymous
January 01, 2003
Sharath, we have seen other reports of this issue and I think we know the cause. The .XLS extension has been used for many different versions of Excel, and the file format has been different for each (2, 3, 4, 5, 95, 97-2003).However, the OMPM scanner only supports the Excel 97-2003 format. Any file with an XLS extension that is not the Excel 97-2003 (BIFF8) format will produce an error because the scanner was not architected to support it. The workaround we recommend is to open the file in Office 2010 and then save it again. Unfortunately this is the only workaround that I have at this time.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
hawks5999, we've tested the space issue you mentioned and this does not affect the use of the setting. However, I should also point out that the SkipOldAccessed and SkipOldModified settings are used only when deep scanning is enabled and are ignored during light scans. Are you running a light scan by chance? We are in the process of updating the OMPM docs to reflect this.Anonymous
January 01, 2003
Tania, are you using the August 2011 version of OMPM? Can you share the section of your ini file that's not working?Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Bweetle, you're right--the 4.0 download seems to have been removed from the page. I can't even find it by searching. I did however find the 3.0 SP1 version, and it is supported for 32-bit systems running OMPM. You can find it here: www.microsoft.com/.../details.aspxAnonymous
January 01, 2003
HPN, I don't think the scan should be taking that long. Your best bet is to contact MS Product Support for assistance.Anonymous
January 01, 2003
The comment has been removedAnonymous
January 01, 2003
Puff-Hippchen, for an issue like what you're seeing, it's best to call Microsoft Product Support for assistance. There could be an issue with SQL that will require more investigation than what we can cover via the blog.Anonymous
January 01, 2003
Hi Dave, thanks for your question. Unfortunately OMPM does not offer the same type of presentation-ready reporting that MAP offers. Our OMPM team suggests building a report in Excel by querying the SQL DB directly, or using the file export functionality in the Access report to get the file list, and then write something custom to report on it.Anonymous
January 01, 2003
The comment has been removedAnonymous
August 29, 2010
Is there any way to read the output without creating an SQL DB? I have 4 Access DBs with about 250,000 lines of code I want to check and that is it.Anonymous
August 30, 2010
In OMPM, offscan.exe and ofc.exe can be used without a database. The output of offscan.exe is an XML scan results record per file. Without a database, you would need to parse those files manually, either by reading them or searching through them with Windows. The schema is straightforward, but this is kind of cumbersome. You can also try installing SQL Express, which is free and can handle up to 100k scan records. OFC can be pointed directly at files to convert them by configuring ofc.ini.Anonymous
September 03, 2010
OEAT - "There was an error downloading the vendor list" When compiling results in OEAT, it always seem to fail to retrieve vendor details from Microsoft. Have you see this before / know how I can get roudn it (e.g. downlaod sepratley?) I get prompted to download as follows: "Vendor List Download
To compare resutls with known vendor add-ins that work with the latest version of Office, you need to download the vendor list from Microsoft. Would you like to download that list now? YES / No" After selecting "Yes" it fails with the following message: "Download failed
There was an error downloading the vendor list. There is either no network connection, your proxy settings are not configured correctly, or the web service is currently unavaialble. Please try again later. However if this problem persists, please contact your administrator" However - I know my proxy settings are fine and I can download other files no problem. What location is it trying to contact (so I can try manually) Thanks
- AL
Anonymous
September 04, 2010
Hi, I got this error when im going to connect with the db using de ompm.accra file Microsft Office Access "Syntax error in date in query expression ´#04/09/2010 ..'" any solution for that, ThanksAnonymous
September 19, 2010
I get an error importing data. Importing extracted data ERROR: Import operation failed Error opening the data file ANy help would be appreciatedAnonymous
November 03, 2010
How long time will it take to scan a file share with 13 000 000 files? I have the Macro scan and SkipOldAccessedFile enable. The scan have been running for a week now.Anonymous
November 19, 2010
I am trying to convert .mdb file to ms access 2010. but it gives error like Database too large, not copying. Access properties skipped. Please help me.Anonymous
November 21, 2010
Was able to get as far as you ran through in your first blog. However, I now need to present the data to the executive team. Does OMPM or the OMPM Access Report Viewer allow for any type of exporting into excel or docs. For example, MAP does a real nice job of putting together results in to presentation ready reports. Any advice on how I can now go about presenting the OMPM results would be greatly appreciated. Thx!Anonymous
January 07, 2011
I am run mport of data to Sql sever 2008 r2 with the following command C:OMPMDatabase>ImportScans.bat hostnameSQLEXPRESS ompmdb c:ompmscandata And get Microsoft Office Migration Planning Manager version 2.0 Batch Scan Import Tool Copyright (c) 2010 Microsoft Corporation. All Rights Reserved. According to data in the database another import process is in progress. Only one import may be run at a time or the database may be corrupted. Please finish the prior import before beginning a new one. If imports are not in process but were interrupted instead, it is safe to reset the ImportInProgress bit and restart the import. To reset the ImportInProgress bit, run the following at the command prompt: osql.exe -S E25DTFW00117SQLEXPRESS -d ompmdb -n -h-1 -E -Q"Update Process_Contr ol Set ImportInProgress = 0" Press any key to continue ….. Have driven the proposal that stands, without any help. I have restarted sql server and it still the sameAnonymous
January 13, 2011
Its very understandable to me . But I have some doubts. 1)Can we use this tool without SQL Server 2008? 2)Do we need to have Microsoft Office 2007 ? or is it ok with 2003 also?Anonymous
March 25, 2011
Are there any partners that will come in and do the testing and any required remediation?Anonymous
April 05, 2011
I get an error importing data: Illegal xml character.<?xml version="1.0"?><Result State="FAILED"><Error><HResult>0xC00CEE2B</HResult> <Description><![CDATA[Illegal xml character. ]]></Description><Source>XML SAX Parser</Source><Type>FATAL</Type></Error></Resu lt> Help me. ThanksAnonymous
April 19, 2011
It really is hard to imagine something more complex. It took me all day to download and install all the bits and pieces I needed, many not mentioned above. And surely editing INI files and running software from the command prompt are things of a bygone era! I can’t help but suggest that needing such a process to handle the volume of incompatibilities arising between Office 2010 and its predecessors is nature’s way of telling you to modify 2010 to remove most, preferably all of these incompatibilities. I haven’t got time to fix them all myself.Anonymous
July 19, 2011
Can someone validate what looks like it may be a bug in the .ini file included in the download and in the documentation above on this page. Specifically the space in the lines SkipOldModifiedFiles =0 and OldModifiedDate =2005/01/01 We've performed a scan of several million files changing the 0 to 1 and setting an OldModifiedDate. The skip setting seemed to be ignored in the scan.Anonymous
July 29, 2011
I got this error too and I can't find any solution against! :-/Anonymous
August 26, 2011
I have just tried to import data with ImportScans.bat and get the following….. C:OMPMDATABASE>ImportScans.bat .ompm ompmdb c:ompmscandata Microsoft Office Migration Planning Manager version 2.0 Batch Scan Import Tool Copyright (c) 2010 Microsoft Corporation. All Rights Reserved. Importing Data Do not interrupt this process or launch another import process. Importing data may take several minutes depending on the amount of data extracted. Extracting files from "c:OMPMSCANDATAScan_W7WORKPC{68EB0460-651F-4EF2-8182-86B4565CE72B}00001.cab"... Importing extracted data... It just seems to have stopped! Do you have any suggestions.?Anonymous
October 21, 2011
how to generate ompm report for multiple client machine at a time, I tried this out Folder=\jillT400C$, but when im specifying multiple machine its not accepting.Anonymous
January 17, 2012
I have the whole procedure ecept step 6 ( Install the Microsoft SQLXML 4.0 SP1 pack) I can't find SQLXML 4.0 But I have installed Microsoft Core XML Services (MSXML) 6.0 SP 1 Afterwards if I want to do the importscan I have got an message that I must install SQLXML What must I do ?Anonymous
June 17, 2012
Hello, When I tried importing the completed OMPM scan results into a SQL 2008 Express R2 dbase, I keep getting "Login failed for user '<domain>administrator'", Cannot open dbase "OMPM004" requested by the login. The login failed. Failed to Create Indexes. I've done this one two different dbases (same server, same OS), and keep getting the same error. both dbases were created using "<Install_Folder>DatabaseCreateDB.bat" tool. Server is physical, 4GB RAM, Server 2008 R2 OS. Can anyone assist? Please let me know if you need more info in troubleshooting.Anonymous
July 24, 2012
Hi Jill, We are using using OMPM 2010 for performing the assessment on office remediation. When i have scanned couple of excel files and when i go to the access db to pull the report i got couple of files which couldnt be scanned and its says tool issue. I have checked for scanned errors and its says "File Type Not Supported by OMPM Deep Scanner." Those are the excel 2003 files and i couldnt get much info on this error. Could you please help me with more information on this issue. Thanks, SharathAnonymous
August 07, 2012
Hi, I got this error when im going to connect with the db using de ompm.accra file Microsft Office Access "Syntax error in date in query expression ´#04/09/2010 ..'" any solution for that, Thanks
same here. Any solutions?
Anonymous
August 20, 2012
The comment has been removedAnonymous
October 09, 2012
Hello, Thank you for taking the time to create this article. It is most useful. I followed your steps word for word and have run into an issue which is similar to one of those mentioned above, but the solution didn’t help. I have installed SQL Express 2008 R2, MS SQL 2005 Backward Compatibility and the SQLXML 4.0 SP1 pack on a Windows XP SP3 machine. I have local administrator privileges to this machine. I also installed and ran OMPM on this machine as well. The offscan.exe ran successfully and created a txt and cab file in the C:ompmscandata folder. I was able to create the ompmdb successfully via the command prompt. I was able to connect using the ompm.accdr file successfully as well. The problem arises when I am trying to import the scan into SQL. When I run ImportScan.bat .ompm ompmdb c:ompmscandata I get the following error. C:ompmDATABASE>ImportScans.bat .ompm ompmdb c:ompmscandata Microsoft Office Migration Planning Manager version 2.0 Batch Scan Import Tool Copyright (c) 2010 Microsoft Corporation. All Rights Reserved. According to data in the database another import process is in progress. Only one import may be run at a time or the database may be corrupted. Please finish the prior import before beginning a new one. If imports are not in process but were interrupted instead, it is safe to reset the ImportInProgress bit and restart the import. To reset the ImportInProgress bit, run the following at the command prompt: osql.exe -S .ompm -d ompmdb -n -h-1 -E -Q"Update Process_Control Set ImportInProgress = 0" Press any key to continue . . . So I do run the osql.exe -S .ompm -d ompmdb -n -h-1 -E -Q"Update Process_Control Set ImportInProgress = 0" command and then get the following error as well. Failed to load resource file OSQL.rll. The system cannot find the file specified. Since I had scanned only one machine, I had deleted and recreated the db but that didn’t help. I have run out of ideas. Any help in this regard will be highly appreciated!Anonymous
October 15, 2012
Hi Jill, Yes, I did get the issue resolved. I had to edit the ImportScans.bat file to get it working. I changed the osql.exe to sqlcmd.exe That did the trick!Anonymous
October 25, 2012
The comment has been removedAnonymous
November 11, 2012
Will ompm deep scan files that are in use?Anonymous
November 13, 2012
Me again. I keep getting the following error on one set of folders I am scanning HRESULT = 0x80070008 Can anyone shed any light onto what might be the cause? I have stopped the scan and restarted from another machine but this started again. Any ideas? ThanksAnonymous
December 08, 2012
The comment has been removedAnonymous
December 08, 2012
Hi, I am having the same issues as George listed above were the import will just hang. i have deleted the database recreated the database disabled the AV software rebooted the machine tried different data It makes no difference the import just hangs, I have left it for over 8 hours. Would it make any difference if the data was imported already? The permissions are correct as the user has FC over all of the folders and I am running the CMD window as Admin Can you please advise?Anonymous
February 26, 2013
The comment has been removedAnonymous
March 04, 2013
i got stuck at h. Wait for the installation process to finish, and then close the wizard and the SQL Server Installation Center. with a message under the progress bar as Install_DotNetCore_Cpu64_Action please help thanksAnonymous
May 21, 2013
Hi, I have the same problem Joseph! Still no issue?Anonymous
July 23, 2013
Hi i am having trouble opening the access file it gives me a error (runtime) with eventid 300 . Any help on this? ThanksAnonymous
July 23, 2013
Hi i am running into a problem that i start the file ompm.accdb and get a new runtime error with event 300 did somoene have/or had this problem?Anonymous
July 28, 2013
I have been testing the OMPM tool (ofc.exe) to convert Office 2003 files in bulk to the Office 2007 format (XML). The problem I encounter is that we convert the files and OFC places them in a specific directory that follows the same structure of the source path. But we end up with the original files plus other non Office files in the source path, and now a target path that contains all the converted files. How can we remove the files that were successfully converted? Assuming I have a media copy or a backup of the original files, I feel I can discard the converted files. Another option would be to move the converted files out of the source path into a separate folder, and place the XML version in their place. This way, we are not detaching the Office files from other documents that belong together.Anonymous
January 16, 2014
Hi,I Have 64 bit version of Microsoft Access 2010 installed on my system.but to run ompm.accdr you need the 32 bit version of same.So do we have any work around to solve this problem, except then getting the 32-bit version installed?Thanks.Anonymous
August 03, 2014
Unable to create a Database using CreateDB.bat from tools.
Getting an error as
"Runtime Error!
Program: c:WindowsSystem32cscript.exe
R6034
An Application has made an attempt to load the C Runtime library incorrectly.
Please contact the application's support team for more information.
"
Please help with solution or let me know where to raise this issue.
I had followed above article as is, but stuck up after step 6. :(
Thanks in advance.Anonymous
November 09, 2014
The comment has been removed