Some build specifications change on different machines

Hi all,
I often need to move my LabVIEW projects from a machine to another one. In this cases, I copy all the contents of my project folder in the new machine.
My projects are built without errors, but some build specifications are not kept.
Build specifications that are not maintained are additional installer list (see attachment).
In the machine 1, I include only Math kernel Libraries and NI VC2008MCMS.
When I open the same project on the Machine 2, all the elements in NI LabVIEW Run-Time engine 2012 SP1 f3 list are checked. (see attachments)
Thank you
Attachments:
machine1.png ‏5 KB
machine2.png ‏5 KB

Hi AC_85,
have machine 1 and machine 2 the same installed software? Is it the same version? Maybe on the machine on which you copy your project some additional installer is not installed.
You could try to Duplicate the entire project (from project explorer File >> Save as >> Duplicate project >> Include all dependencies) before moving it from machine 1 to machine 2.
Hoping this will help you.
Best Regards.
Cla_CUP
NI ITALY

Similar Messages

Transfer build directory to a different machine : linux

Hi,
Can we make a build directory of Berkeley DB which is portable to a different system which does not have root access?
Thanks

Hi Rajesh,
Please check below link.
Move SAP Business One Application to a new server - how?
Client bought better server for SAP B1 - steps to change the server ?
Change server B1 Share
Moving DB from one SAP B1 9.0 to another SAP B1 9.0 Server. Same DB.
Hope this helps
Regards::::
Atul Chakraborty

Programmatically Changing Build Specifications from command line

I use a batch file that calls a VI to build several LV projects. I found the article http://zone.ni.com/devzone/cda/epd/p/id/5051 to get started and build projects; however, I was wondering if anyone has been able to change build specifications without opening the Application Builder dialog? -> I would like to build an app. with a version number using the command syntax: labview.exe <mybuild.vi> -- "project1.lvproj" "version number"
Any thoughts regarding this problem?
Thanks,
Adam

I have done some research and there doesn't seem to be a way to change the version number when building a project with this method. If I find out otherwise I will post to let you know but I don't think it is possible. I would look for another way to accomplish what you want by incorporating the version into the file name or something like that.
Eric A.
National Instruments
Distributed I/O Product Support Engineer

I recently purchased a used imac with os 10.6 The problem I am having the admin in accounts in system preferences I would like to change so I can download some items I have tried different things to do this but I cannot figure it out. thanks

I recently purchased a used imac with os 10.6 The problem I am having the admin in accounts in system preferences I would like to change so I can download some items I have tried different things to do this but I cannot figure it out. thanks in advance.

Thats the problem I bought it from a very large thrift store. i went back asked the person where I bought the computer he said we can not give you the password. I thought buying it there was a good idea because not only was it a nice deal but it was like I was maknig a donation. I know that i messed up because i do not have the installation disk. I bought it without thinking. Until recently I was still using an old G4 9.0 os. I guess you can say I have been out of the loop for a while.

Why differences in the way different machines handle the same code??

OK, I've posted some other threads re some difficulties in getting the same code to function identically on, not only different platforms, but even on different machines running Windows!
Here's another, and I would really appreciate an explanation:
I have a tree control. Per the user's request, I made the right button function the same way it does on MS File Explorer: When they right click, the currently selected nodes are compared to the node they clicked over. If they clicked over a selected node, then the context menu for the nodes selected is displayed. If they clicked over a different node, then the selection is changed to the new node and the context menu displayed. If they right click over the tree control, but not a node in the tree, then the selection is cleared and no context menu is displayed.
Works great on my machine.
However, on some machines, no context menu is displayed, nor is the node selected... UNLESS THEY ALREADY HAVE A NODE SELECTED. I.e., if they have no nodes in the tree selected, they cannot display the context menu by right clicking on a node, nor does the selection change to the node they right click over. It only works if they already have something selected.
My app is distributed as an executable jar file and I am distributing the JRE with it, so there are no class path issues or differences in the JDK. Basically, my problem can be paraphrased as: Why doesnt' Swing behave the same way on different machines...? At least why not the same on the eame machine.
It's driving me nuts to think that I've resolved some UI glitch only to find out that, no, it's only fixed on some machines, not others.
Thanks.

Well, I normally develop on OSX and then deploy to Windows. But, this last build I have switched to Windows XP. The kinds of differences I am seeing are subtle: what triggers a repaint of the UI and now, it seems, what events are getting triggered by mouse clicks.
My deployment is an executable jar file, therefore it uses the manifest in the jar, not any classpath variables. I deploy an entire JRE along with the app, and the bat file that launches the app ensures that is the JAVA_HOME I'm using.
I can only guess that it's some underlying difference in versions of the platform and OS that causes this.
Here's the entire code for this latest issue re the popups:
        private void maybeShowPopup(NodeInfoTree tree, MouseEvent e) {
            if (e.isPopupTrigger()) {
                // They clicked the platform dependent popup trigger...
                int x = e.getX();
                int y = e.getY();
                TreePath[] selectedPaths = tree.getSelectionPaths();
                if (selectedPaths == null) {
                    selectedPaths = new TreePath[0];
                TreePath clickedPath = tree.getPathForLocation(x,y);
                if (clickedPath == null) {
                    // they right clicked, but not on a node, so clear the selection and return
                    tree.clearSelection();
                    return;
                } else {
                    // They clicked on a path, so let's see if it is a selected
                    // node. Search the selected array of paths, short circuiting
                    // out if it is found...
                    boolean foundInSelection = false;
                    for (int i=0; (!foundInSelection && (i < selectedPaths.length)); i++) {
                        foundInSelection = clickedPath.equals(selectedPaths);
if (!foundInSelection) {
// They right clicked elsewhere than the selection, so
// reset the selection to the new path...
tree.setSelectionPath(clickedPath);
final TreePath menuPath;
selectedPaths = tree.getSelectionPaths();
if (selectedPaths == null) {
return;
} else {
menuPath = selectedPaths[selectedPaths.length-1];
// Since they did click on a node, now we need to determine
// what popup menu should be displayed...
tree.scrollPathToVisible(menuPath);
NodeInfo ni = (NodeInfo) menuPath.getLastPathComponent();
// If the last path component is null, then they don't have
// anything selected, so we do nothing
if (ni == null) return;
// See if the Node is overriding our default popup menu...
com.harcourt.applications.tgen.browser.nodes.NodeMenu nodeMenu = ni.getMenu();
nodeMenu.activate(tree.getView(),ni);
JPopupMenu popup = (JPopupMenu) nodeMenu;
if (popup != null) {
popup.show(e.getComponent(),
e.getX(), e.getY());
The nodeMenu.activate call is just used to check whether or not certain menu options need to be enabled or disabled before displaying the menu. My theory right now is that, on some of these machines (all windows), a right click of the mouse is not generating a mouse event unless they have already something selected. I don't think it's a focus issue, because if they left click to select a node, and then ctrl-left click to de-select it, the right button then no longer generates a popup menu. They must select a node, then right click. Maybe there's no mouse event generated, or maybe this line is failing on some machines?:
TreePath clickedPath = tree.getPathForLocation(x,y);

Build Specification does not include all files for my VI.

Hi!
As a part of a semester project i have build a VI to control a filtration unit. The VI is working fine on my computer, but I graduate next month and I have to deliver the files on to a person on the university. The problem is that even though i use the "Build Specification" function (i use LabView 2011 Professional Development System), files are still missing when the program is started on the new computer. A warning in the project file indicates that files are missing or removed to a different location. A file named pid.lib is not found, and it seems like the path to each file is the same as on my computer, but the build specification doesn't change that to fit the new computer.
I am a LabView newbe, and I have searced this forum and help files to try to solve this by my self, but now my time is becoming limited. Can anyone help me with this?
Henrik jepsen
Masterstudent Chemical Enginnering
Denmark
Solved!
Go to Solution.

Hi Henrik
You can see what versions of LabVIEW and which Toolkits is installed in Measurement and Automation Explorer (MAX). If you Open MAX, and Select "My System" --> "Software in the left menu, then you can see all software installed.
If you click on the LabVIEW installation. In this case LabVIEW 2011, you can see all toolkits installed.
When you run a LabVIEW project / application on another PC, LabVIEW will use a defined priority of where to load the files from. This is specified in Tools --> Options --> Path --> VI Search Path.
So LabVIEW will frist try to find the VI/VI library in the folder of your project and if the VI is not located there it will look for it as a build function in the vilib, userlib or instrlib folders of LabVIEW. These folders contains VI's and VI libraries installed with LabVIEW.
In this case, as mentioned above you properly don't have the same toolkits installed on both machines. Therefore the PID.lib is not found in the vilib folder as it should be, and thereby you get the error. You can confirm this by reviewing the installed modules as mentioned above.
Best Regards
Anders Rohde
Applications Engineer
National Instruments Denmark

Programmatically create build specification

Here's my problem. I have several dozen projects, each of which contain the same VIs (more or less) but are for different hardware configurations. In particular, they all contain 1) a PXI target that contains a unique EtherCAT configuration, 2) a unique startup VI that should run on the PXI, and 3) other peripherals that may have build specifications as well (e.g. FPGAs). Occasionally I need to make a change to the way our code builds, and that means I need to open every single project to make the change. Since the projects are very large, this takes a long time.
My solution is to create a separate program whose job will be to open the selected project, create build specifications with the settings that are common across all the projects, allow the user to select unique aspects such as the startup VI for the PXI, and build any/all other build specifications necessary for the selected project.
I found here a topic disucssing modifying build specifications programmatically, but since I want to create a build specification, I would need to know what every single tag is, how it is used, what its allowed values are, etc. Is there some documentation I can refer to for this? Or better yet an example VI that someone has already put together?

The other thing to remember is that at the end of the day, the output of the build specification process is just a string that happens to be part of an XML file (the *.lvproj).
You can always check your work by opening the project file with a text editor and verifying that it is correct. Just remember that because this is not documented or supported, it can change at any time. So if you are successful, anytime you update LV you will need to recheck this code to make sure it still works.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Generally when creating a Word file from either a Mac or Win7 pc and opening it on two different machines (either one first) it always prompts that the file is open and will be opened as read only. However opening a CSS file does not prompt that it is alr

Generally when creating a Word file from either a Mac or Win7 pc and opening it on two different machines (either one first) it always prompts that the file is open and will be opened as read only.
However opening a CSS file does not prompt that it is already open on or from any machine which is causing code edits to be lost.
What we found from out testing:
- The file can be saved from one user to the server and WILL NOT PROMPT on other machines until the saving machine has the Dreamweaver program closed completely
- The file can be closed and Dreamweaver minimised to the launch bar but it still will not register on other machines that it has been changed.
- Also, until the Dreamweaver program is closed on the machines, it will continue to open it's saved version of the file.
Example Scenario:
- User 1 opens test.css (which is 2000 lines) and adds some code to the end of the file to bring it up to 2500 lines
- Meanwhile User 2 opens test.css as well (opens as 2000 lines as User 1’s edits have not yet been saved) and adds in code to bring it to 2300 lines
- User 1 saves his file and closes it - but Dreamweaver is still open.
- User 2 also saves his file and leaves Dreamweaver open.
- The server will report the size and last edit of the file the same as User 2 as he was the last person to save it (and if you open from the Win7 Machine it will show as User 2’s 2300 line version)
- If User 1 then open's the file again (from either the 'recent' in Dreamweaver OR clicking on the file directly in Finder...which version opens.... The version that User 1 saved! Not the true version on the server, but the version that User 1 edited and saved with 2500 lines in it.
- Same for User 2, he will open 'his' version with 2300 lines in.
Other information:
- Files are opened directly from the server
- Sometimes the users will save incrementally and re-open
- Most of the time users will save incrementally and keep the files open
- The users will never not save incrementally and just save when closing the file once finished
- The users are usually working on the files all day
- It is always the bottom lines of code that are lost. It could be a case of the two versions being mixed up and cutting off the newly added lines based on the line count (possibly).
It is as if Dreamweaver is holding a cache of the version locally and then only properly looking back to the server when it has been completely closed. It is very difficult to see how the server is causing such an impact on these files, there are very few logs which are giving any indication to the root cause of the problems.
Anyone know if this is a known issue?
Is there a way that there can be a featured implemented on the server that doesn't allow another user to open a file if it is already open on another machine?
Thanks

Your server file handling has nothing, and really nothing to do with Adobe software. If files don't get locked for (over-)writing and/or lose connection to the program opening them, then your server is misconfigured. It's as plain and simple and that. Anything from "known file types"/ file associations not being set correctly, MIME types being botched, crooked user privileges and file permissions, missing Mac server extensions, delayed file writing on the server, generic network timeout issues and what have you. Either way, you have written a longwinded post with no real value since you haven't bothered to provide any proper technical info, most notably about the alleged server. Either way, the only way you can "fix" it is by straightening out your server and network configuration, not some magic switch in Adobe's software.
Mylenium

Use of "Open FPGA VI Reference" function --- Build Specification vs VI vs Bitfile

When using the "Open FPGA VI Reference" function in a LV2012 cRIO application, there are 3 options: Build Specification, VI, or Bitfile. What would be the reasons for selecting one over the others? Does it affect the resulting startup.rtexe when the cRIO application is built? I searched through the help and in these forums, but I don't see criteria for selecting one over the others; maybe I missed it.

Hello Chris,
Apologies in advance for a long reply.
The reference method won't change the functionality of your rtexe.exe. They all end up dropping a bitstream, based on a bitfile, onto the cRIO's FPGA.
To a degree, the method used to reference the FPGA code is a matter of taste, but there are situations where one method is better suited than the others.
Reference by VI:
Setting the configuration options to open reference by VI is helpful during development when you are making changes to an FPGA VI often and building/testing using the same spec. When this option is used, a bitfile is selected based on the default build specification for the project. A project may have only one default build specification. You can make any build the default by checking the option under the Source Files category in the build properties. The default build is indicated in the project explorer by the green box around the builds icon.
Reference by Bitfile:
This option references a bitfile directly. Through the configuration window, you can select one specific bitfile to open a reference to (this is not dynamic and does not change unless you physically go make a change to that path). If you're using this method, it helps to give your bitfiles more meaningful names than the ones that are automatically generated by LabVIEW. When you run subsequent compilations off of the same build specification and do not change the bitfile nname or path in the build configuration, the old bitfile is overwritten and replaced with the new one. When you are using this option, it is critical that you keep up with which bitfile is the one you want to be using. There is an option now that will help alleviate any problems referencing by bitfile through the Open FPGA VI Reference function. There is a new VI called Open Dynamic Bitfile Reference. It is typically used when you want to chose a specific bitfile to load depending on something in your host code (a configuration option etc) - but it allows you to dynamically reference a bitfile on the block diagram by path.
Referency by Build Specification:
This option is good for when you want to always use a bitfile that is associated with/compiled with the same build configuration. Say you have two options for top level FPGA VIs in your project (each with its own build spec). Both of these VIs have the same interface (read/write controls, DMA) but they run different algorithms or something. This is nice because you can easily switch your host application between them by picking the build spec associated with the FPGA VI you want to use. In this type of sutation, referencing by VI is no good because you can only have on default build spec.
cheers.
Matthew H.
Applications Engineer
National Instruments

Instrument Control Build Specifications

Dear Sir:
      I am trying to build a working *.exe instrument control program. This is a simple program which only queries my test instrument with a *IDN? command.
      The program fails to call my instrument driver and the program also runs on boot up when (running under normal conditions) it should wait for me to input the GPIB address of my test instrument.
      Let's begin with the failure of Labview to communicate with the instrument driver.   This is some background information.
       When I run the program as simple *.VI in the Labview environment, the program runs perfectly.    No issues.
       When I use Agilent Connection Expert or MAX to communicate to the test instrument, communication is established and there are no issues - I receive a reply, connectivity is established.
        After I build the *.VI into a *.EXE program, this is where the program's issues arise.
       The *.EXE program fails to initialize correctly and fails to establish connectivity with my test instrument.
        Here are some issues that I have noticed about the program running in *.EXE mode
1) The program runs on "boot up" when you click on the *.EXE program.   In *.VI mode, the program does not run on boot but waits for the user to input the GPIB address of the test instrument - program run is designed to be enabled by the user.
      I do not believe this is the source of the problem but only an incidental consequence of the problem.   If I stop the program and input the GPIB address, I receive a message about not being able to communicate to the driver.
2) Once the *.EXE program runs, there is a condition whereby the operating system cannot close the program and WINDOWS itself cannot shut down itself unless I manually close all the programs associated with the *.EXE program in the WINDOWS operating environment.
3) If the labview program and *.EXE program are closed but the operating system is still running, Agilent Connection Expert and MAX can no longer communicate with the test instrument.   They no longer see the test instrument.
It is obvious that the *.EXE program is making a change which is causing the operating system to "hang" on shutdown and is also preventing the other programs from operating as they should.
I believe the source of my problem may be how I programmed my build specifications.     In reply, can you please tell me what are the minimum requirements for the build specification so that my test instrument can reply to a simple *IDN? query?   What files are normally required for a successful build?
Other information as to the source of my issues are welcome as well.
Thank you.
Solved!
Go to Solution.

Thanks for you advice.
I think this problem is a lot easier than you might think.   I just started using Labview and the *.VI is super simple. I am away from my development computer right now so I can't post it.
The information I need to know right now are the typical files that are needed to be added in the build.
I found this quote that I found on a webpage to be interesting, (although I am not building an installer):
" Do I need to include NI-488.2 2.7.3 module if I use only basic GPIB Write.vi and GPIB Read.vis in my project?
Yes, if you are making an installer ..."
This is a link to the webpage:
http://forums.ni.com/t5/LabVIEW/Uninstalling-LabVIEW-after-an-application-EXE-build/td-p/1553310
My program involves only simple reads and writes using NI-488.2 calls to a test instrument.   A simple list of files specified with filename extensions to get me started would be appreciated.

Any way to have two identical versions of iTunes on different machines?

Hello, probably a fairly basic question, but I'm quite a new iPod/iTunes user and need some urgent help.
I have my iTunes and music library set up fine on my PC with Windows XP, and all of the according media is stored on my iPod. But I would like to transfer all of my existing library to my laptop, which runs Vista, so effectively having TWO identical libraries to the same user, but on two different machines. I'm wondering if anyone knows the easiest way to do this? I've tried a direct transfer and then import on my iTunes library (with the 'iTunes music' folder, which for some reason contains about a fifth of the music that is actually in the library itself), but this didn't work, as only about 700 of 5000 or so songs showed up in the new iTunes library (on the laptop)!
Any help? Hope this makes sense. Thanks.

Yes, it can be done, but it's not the standard thing to do. The first thing to note is that iTunes contains full path references to all your media. Windows XP & Windows Vista have different naming conventions for the default documents folders so under XP you'd expect to find the iTunes library at C:\Documents and Settings\<User>\My Documents\My Music\iTunes whereas under Vista it will be at C:\Users\<User>\Documents\Music\iTunes. If you are copying your library from XP to Vista you should put it at exactly the same path that it had on XP and then tweak the options in the Vista version to point to your desired location.
Connect your laptop & desktop together over a network & share the Music folders on both. Grab a free tool called SyncToy 2.0 and use it to create a pair of syncronised folders. This will allow you to make changes to one library, and then connect the two machines and re-sync. As a bonus you will be able to auto-sync your iPod with either library. It only becomes difficult if you make independant changes on each machine between syncing - the most recently updated files should overwrite the older ones, but the library can end up with out of date information. The following tools can help out here.
*Adding new items/removing orphans*
Try iTunes Folder Watch or iTunes Library Updater. Folder Watch is much faster on the adding files front, can be set to run in the background and includes a useful exclusion feature, however it’s really slow at removing orphans. iTLU is better for this although doing it manually after looking at a list of proposed removals generated by Folder Watch is probably faster still. iTLU can also be set to update iTunes when you've used 3rd party tools to change tag info.
Disable Windows Media Player's "Automatically update missing information" feature on both machines as this has a tendacncy to "touch" files without adding useful info. and wipes out the iTunes "No. of Tracks" field.
tt2

Problem with NIReport.llb\Print HTML Report using IE.vi on different machines

We have 5 machines here in our workgroup which have the same state regarding security patches and other system updates. We recently found out that there is a problem with the NIReport.llb\Print HTML Report using IE.vi on the different machines.
If I would open the VI on MachineA the control could be loaded. If I would open the VI on MachineB the control could be loaded. If I would copy the VI from MachineB to MachineA and open the VI the control could not be loaded. If I would copy the VI from MachineA to MachineB and open the VI on MachineB the control could be loaded. MachineB could load the version from MachineA and MachineB but on MachineA only the own version will load. I have seen that both versions have the same GUID for the Microsoft Webbrowser but are different in some other aereas.
Since printing HTML Reports is part of the application which will be distributed as application I want to know if someone else have seen such a behaviour or has got problems distributing an application.
Also I want to know which additional information is stored in an Active-X container about the control beside the GUID.
We have Win XP Prof SP2 with MS IE 6.0.2900.2180 on all machines in the workgroup.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

Hi Tom,
this is the VI <vi.lib>\Utillitiy\NIReport.llb\Print HTML Report using IE.vi copied from a machine that can load and run the VI and it will print. On this machine the control in the VI is white.
This VI will give the "Control could not be loaded" message on my machine.
The file shdocvw.dll is 2006-10-23 16:18 size 1.460 KB and I verifyed that both machines have the same version of this file.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions
Attachments:
Print HTML Report using IE.png ‏11 KB

Can I run 2 different domains with same name but on 2 different machines?

I am trying to setup 2 domains with same name (sharedcds1) on 2 different machines (Machine1 and Machine2).
          When I start the weblogic managed server 1 (sharedcds1managedserver1) on Machine2, it throws an error saying it has some conflicts with the managed server 1 running on Machine1. How did the managed server of one machine know about the other server. Can I run 2 different domains with same name but on 2 different machines?
          Here is the error in the log -
          <Jun 14, 2005 10:53:29 AM EDT> <Error> <Cluster> <BEA-000123> <Conflict start: You tried to bind an
          object under the name weblogic.transaction.coordinators.sharedcds1managedserver1 in the JNDI tree.
          The object from 4596206652609838848S:130.170.61.153:[9505,9505,-1,-1,9505,-1,-1,0,0]:sharedcds1:s
          haredcds1managedserver1 is non-clusterable, and you have tried to bind more than once from two or m
          ore servers. Such objects can only be deployed from one server.>
          <Jun 14, 2005 10:53:29 AM EDT> <Error> <Cluster> <BEA-000123> <Conflict start: You tried to bind an
          object under the name weblogic.transaction.coordinators.sharedcds1managedserver1 in the JNDI tree.
          The object from 8842351474821025197S:130.170.61.154:[9505,9505,-1,-1,9505,-1,-1,0,0]:sharedcds1:s
          haredcds1managedserver1 is non-clusterable, and you have tried to bind more than once from two or m
          ore servers. Such objects can only be deployed from one server.>
          Thanks
          Satish

Yes you can. Make sure that domains configured to use different multicast address. WLS uses multicast for communications between nodes in domain.
          although your configuration will work, you could have troubles if you going to execute inter-domain calls between domains/servers with the same names.

Can I labled the same song to more than one albums? As you know, some songs are repeated in different albums.

Can I labled the same song to more than one albums? As you know, some songs are repeated in different albums.

You can make a copy of an existing song, then change the album, artwork and track number details. You cannot make the same physical file show up in two different albums.
tt2

How to create a table of contents (TOC) linking to specific pages of different (multiple) PDFs

Hi All,
I would like to create clickable Table of Contents (TOC) that can lead to a sub clickable TOC that would lead to a specific page of different PDFs within a folder.
Is that possible?
Secondly, is is possible to create a search box that upon typing a specific word (not related to text within the PDFs), that word to be linked to a specific page of a particular PDF out of many within a folder?
To make it more clear, I have a database of specifications of equipment and drawings of a building, all in multiple PDF files. I would like to be able to unify all those PDFs and if I type the room number of the building to be presented with a menu of choces pointing to services assosiated with that room, being elctrical power drawings, lighting drawings or drawings of Air Conditioning and Ducting associated with that room. So I type a room number, then I get a menu of Power, Lights, Fire Alarm, or Ducting all associated with that room, then if I click Fire Alarm to be directed straight to the drawing within a PDF related to that room.
Thanks

I would say: Try and Error. Create a copy of your document and unmark in the copied document in the document inspector all boxes for the TOC. Then mark them again. Maybe you should also delete the paragraph styles and mark them again. If that doesn't work, try to copy the complete text of your document to a new created one. Maybe that works.
Good luck!
P.S.: If that doesn't work look here. Maybe this helps.

Some build specifications change on different machines

Similar Messages

Maybe you are looking for