Can not import or export MAX configuration

[cirrusio]

Hello all,

I have had a baffling issue that seems to be related to my development computer configuration.  I have a PXI target for which I have configured the hardware via MAX and I have been unable to import or export the configuration via the MAX interface on my main computer.  I have been successful using other computers (for which I have made no firewall exceptions), but for whatever reason, it just doesn't seem to work on this particular computer.  I am using the most recent version of MAX and able to create reports for the hardware configuration, but when I select import or export, I get the Windows spinning disk for several seconds and then...nothing.  There is no feedback or anything to let me know what the issue might be.  Does anyone have any thoughts?  This became a problem recently as I had no current configuration when I experienced a database corruption on the target and am now having to rebuild tasks from notes.

Thanks a lot.

Cheers, Matt

[PatrickLye]

Look at your performance/usage in Task manager. You might see high usage. Look under processes and see if you notice any processes eating up your resources. That may help you find out what is wrong.

Maybe run a repair on your labVIEW software, which I wouldn't do unless there was no other choice.

[PatrickLye]

Rebooting fixes a host of labVIEW problems.

Look at your Windows event logs. That might lead you to a solution.

I see you didn't have to make exceptions in the firewall, but if you have the authority try turning off the firewall and maybe even antivirus just to rule them out.

[cirrusio]

Patrick,

First, this is involving a real-time target and communication with MAX, not LabVIEW.  Second, this is an ongoing issue.  Third, turning off the firewall is bad and should not be necessary.  I am hoping that someone has a suggestion as to maybe a port that I am missing or a service that is not turned on.

Thanks, Matt

[JoshuaP]

Also make sure you have the same versions of the drivers on your host that you have on your target.  The Import/Export wizard loads the local host drivers, which communicate to the remote systems driver.  In some cases if the versions don't match the driver will error out. I know this is the case with DAQmx.

You could also add an outbound firewall rule for the MAX application, however in general this should not be required.  

[cirrusio]

Yeah...like you said, the MAX rule should not be required for outbound.  MAX is open for all ports on TCP and UDP for inbound though.  Maybe I will try the outbound.  All drivers were loaded from this computer that I am trying to communicate on (15 for DAQmx).

[PatrickLye]

"First, this is involving a real-time target and communication with MAX, not LabVIEW.  Second, this is an ongoing issue.  Third, turning off the firewall is bad and should not be necessary.  I am hoping that someone has a suggestion as to maybe a port that I am missing or a service that is not turned on."

MAX is typically running on Windows which can easily lead to diagnosing the issue from Windows. I should have said National Instruments software now LabView, but they all come from the same company.

I'm sorry this is an ongoing issue, but it just came up on my RSS feed not long ago.

Turning off the firewall is not bad if done for diagnostic purposes and then turned back on when you determine that is the issue and you find what exceptions need to be made etc...

Please feel free to list the types of answers you are looking for in the post. It will save time.

[cirrusio]

Patrick,

What are you suggesting that I should be looking for?  This has been an issue before installation of 2015 and continues to be an issue after.  I have gone through several updates of MAX and this is a consistent problem.  So, what do you suggest that I look for in the Window's event logs?  The logs themselves are large given the fact that I have not cleared them...ever. 

Turning off the firewall doesn't resolve the issue.  This suggests that I don't have a service that is required running.

Matt

[PatrickLye]

I'm not telling you what the answer is. I'm simply trying to aid in some steps when a description of no errors was originally given. Like all things diagnostics it is all about educated guesses and isolating possible problems until the actual problem is located.

I have no experience with PXI. I'm using PC control, DAQmx, and cRIO, but I have found that the more complex software gets the more chances of glitches that can be reset by a simple reboot. I'm not trying to belittle your experience with PXI. I do have some experience with MAX, and gaining all the time, but if it runs on Windows it can be affected by the OS, drivers, memory leaks, etc...

Now typically I try change the situation until I see the problem change. Sorry that it wasn't as simple as turning off the firewall, but that can be a very quick and dirty way to isolate problems, and when it doesn't work you just turn it back on. Sometimes turning off network backup software or antivirus software to see if affects the problem is a good idea.

I have two networks at this facility. One is the office network that adds in many things that get in the way of other programs. When at all possible I run everything on my industrial network where I have control, everything has static addressing, and none of the complex problems that can happen due to DNS, DHCP, etc... can get in the way.

Sometimes a program will run fine on my industrial network and I have to isolate for hours when they want it moved to the office network. I'm not saying this is where your problem lies. I'm just trying to lend my meager experience gained in the industrial control and networking fields, and I started doing this in 1985 so there may be some help available here. 

Now, since you have a repeatable problem, even without clearing the Windows logs, which a lot of I.T. departments don't allow all users to do anyway, you repeat your problems a few times while noting the time. Then you can open the event logs and look for any problem indications that correspond with the times you just saw the problem repeated.

Now, if none of this helps, and nobody else with more PXI experience than me can give an answer I typically try to view the traffic between the devices. WireShark, which a free and powerful program is an often go to tool in my kit. I've recently found that it will even monitor the usb traffic, which I'll soon need on a project that I will hopefully be starting next week.

The main lesson that I've learned about Microsoft Software, which I've been actively been using since DOS, is that it is not MAC. This leads to many issues when running programs on it. I've also found that National Instruments software runs much better after cleaning all bloatware off of a system from Dell, HP, Lenovo, or any other vendor. A clean load without all of this bloatware is best, but not all companies will go to that level.

[JoshuaP]

When the Import/Export dialog launches it does read some data from your local MAX database, so its also possible that your local systems database has somehow gotten into a bad state.  

Have you tried deleting all of your remote systems from MAX.  Close MAX and then reopen and re-add the target if it doesn't auto discover it on your local network.  If that doesn't work you may need to use the Reset option from the tools menu, however you will loose all of your MAX configuration.

Also try expanding your local Devices and Interfaces on your PC before trying to launch the wizards to see if that changes anything or shows any additional information.