PI 7.1 components fail self test after SP7 application

Hello: We installed P I (7.1) SP 6 successfully on sandbox and recently applied SP7.
While performing readiness check, any test step related to "cache connectivity test" is failing.
I am using the following Document: "Readiness Check - A compilation of simple and advanced checks for Process Integration 7.1 (PI 7.1) ver 1" document.
Also in the RWB, Business process engine and Adapter engine status shows RED.
Attempted to work thru notes 764176, 1117249 but still facing issue with Cache connectivity test.
Any one having problems with SP7. Help on resolving this issue is appreciated.
thanks, Srini

We applied the following patches and able to clear the issue.
ESPFRAMEWORK07_1-20001918.SCA
SP07 for ESI - ES PROTOCOL 7.10
ESI - ES PROTOCOL 7.10
#OS independent
Application Server Java
ESIUI07_2-20001923.SCA
SP07 for ESI USER INTERFACE 7.10
ESI USER INTERFACE 7.10
#OS independent
Application Server Java
SAPXIESR07_7-10005116.SCA
SP07 for ESR 7.10
ESR 7.10
#OS independent
Process Integration
MESSAGING07_8-20001897.SCA
SP07 for MESSAGING SYSTEM SERVICE 7.10
MESSAGING SYSTEM SERVICE 7.10
#OS independent
Application Server Java
SAPXIAF07_6-20001975.SCA
SP07 for XI ADAPTER FRAMEWORK 7.10
XI ADAPTER FRAMEWORK 7.10

Similar Messages

PCI-6221 fails self-test in MAX but device manager says it's working

Hi everyone,
I bought a few PCI-6221 (37-pin) data acquisition cards and have been able to get one to work but 3 others don't work.
Device Manager sees them and says they work. MAX sees them and when I run Self Test, they fail with error number
-50002. Motherboards in non-working systems are PC Chips M957G and P25G. OS is Windows XP Pro with SP2.
I already tried uninstalling SW and the board, reinstalling SW and the
board...autodetect etc works fine. I even reformatted
the HD on one of the computers and reinstalled the OS. Anyone have any ideas? Thanks in advance. Halden
[email protected]

Thanks Tom for your suggestion to try NI-DAQ 8.0. I just saw it today. Yesterday,
I was able to isolate 3 PCI-6221-37 boards as defective because they all wouldn't work in another computer while
one other identical model card did work in that same computer. I called to arrange to return them to NI and learned
that for these 3, I needed NI-DAQ 8.0. The fourth one was okay
with NI-DAQ 7.5. Apparently, this was a known problem.
I wish NI would have simply notified me that my boards would
not work with the software sent with them and sent the NIDAQ 8.0 CD as soon as they knew rather than have me
waste a day of my engineering time trying to figure it all out. Booo NI.
One of the boards has worked for almost a day under NIDAQ 8.0. I was able to make some progress on the
system I am building. But then it stopped working. LabVIEW
(version 7.0 executable) programs would not open completely
or would open slowly. One that accessed the COM port only (no
data acquisition) did work. MAX opened very slowly or not at all
and when I click on
Devices and Interfaces, the hourglass is up for a long time and finally the + icon goes away indicating that MAX is not
aware of any devices being present. The Windows Device Manager says the board is present and working. Windows
Task Manager lists LabVIEW Runtime and MAX when only MAX is open and indicates that MAX is Not Responding.
I shut down the computer, removed the PCI-6221 board, booted it up again, and MAX is the same way. I uninstalled
MAX and NI-DAQ LabVIEW 7.0 support and then reinstalled them.
Now the MAX loading window is up for more than a minute and NIMAX.exe is listed in Task Manager's processes. After
the first minute, LabVIEW Runtime appears in the Task Manager's
Applications list. After a while longer, the MAX window finally
opens
and MAX is listed in the Applications. I click on the + icon by Devices and Interfaces in MAX and the hourglass appears
and Windows Task Manager says MAX is Not Responding. Eventually, the + icon and the hourglass go away and
the Task Manager lists LabVIEW Runtime and MAX as Running.
I shut the computer off for several minutes, started it up again, and MAX is still takes a long, long time to open.
I haven't put the PCI-6221 card back in because MAX still isn't working.
What do you suggest I do next?
Thanks
Halden

MyDAQ fails Self-Test and will not work with any software

I cannot get the myDAQ to communicate properly. I did everything I could to make sure that the device was detected by the computer. It shows up in Device Manager under Data Acquistition Devices as NI myDAQ and in NI MAX as "myDAQ1", but I receive errors when trying to use it with any NI program.
Trying to self-test or reset the device in MAX gives these errors:
-The self test failed. -88705 The specified device is not present or is not active in the system. The device may not be installed on this system, may have been unplugged, or may not be installed correctly.
-There was a problem resetting the device. Error code: 80040383.
It also gives this error when trying to use the Elvis Oscilloscope:
-Error -200324 occurred at ELVISmx_DAQmx Create Channel (AI-Voltage-Basic).vi:1
Possible reason(s):
NI-DAQmx is unable to communicate with the device. Make sure the device is present in and accessible to the system, is not currently being reset, and is not reserved by another driver such as Traditional NI-DAQ (Legacy).
I have uninstalled and reinstalled and repaired all installed NI products twice. I updated to NI-DAQmx 9.8.0 and am using NI Elvis 4.5. I have checked NI Device Loader and mDNS Responder Service in Services and everything is running properly. I have also tried Reset Configuration Data in NI MAX several times. I turned Fast Startup off as suggested in one article. I have tried plugging it into every single USB port on my computer; all 8 of them. The blue led is on when plugged in, but I cannot figure out why it will not work with any of the software. I am running Windows 8 Pro 64-bit. Also, it completely works on the school computers running Windows 7 without any problems. I would like to have it functioning with all the NI software purchased, but all I want to do is use the oscilloscope software for now. It has honestly been way too much work and a huge loss of time for something that should work out of the box. Please help me resolve this, thanks.
Attachments:
ni_support.zip ‏341 KB

Hi chaka123,
I had already read that article so it wasn't anything I hadn't tried. I did, however, uninstall both NI DAQmx and NI ELVISmx, ran the registry cleaner and then plugged my device in. Now it shows up as USB Flash Firmware Updater. This is actually what it showed the first time I plugged this in out of the box. After much troubleshooting I was finally able to get it to at least recognize it as a myDAQ. This is problem I know others have had.
To answer your questions:
Does the Test Panels work at all?
I am not sure, I didn't try it before uninstalling. Now the Test Panels isn't an option because it is recognized as the Flash Firmware Updater.
Have you tried to delete the device in MAX?
Once again, I cannot because it shows up as Flash Firmware Updater.
Which is the color of the icon on the left side of “myDAQ1”?
It was green before the uninstall. Now it shows the USB symbol.
I tried deleting the driver. When I plugged the device back it, Windows started automatically trying to load a driver for it. Now it shows as NI myDAQ with a yellow exclamation symbol. In MAX it shows as NI myDAQ with a USB symbol. Under Driver Details it says "Windows does not have a driver associated with your device."
What folder can I manually point Device Manager to in order to load the correct driver?
Attachments:
devicemanager.PNG ‏40 KB

PCI-MI0-16XE-50 Failing Self-test

I am using a PCI-MI0-16XE-50 which is failing the self-test in MAX 3.1.1.3004. I have used the E Series Diagnostic Utility which gives the error "Error 10809 occurred at cwdaq: Starting DAQ operation Attempted to start a pulse width measurement with the pulse in the phase to be measured (e.g., high phase for high-level gating)." Windows XP detects the device fine, as does MAX. The obvious answer is that the device is broken, but is it feasible or economical to have the device repaired? What tends to cause this type of problem and/or how can it be corrected?
Thanks,
Brandon

Hello C.
You will need to contact National Instruments for a quote for repairing
you board. If you bought less than a year ago, it may still be under
warranty in which case it would not cost you anything to repair.
However, I would suggest in case you need to pay for repair to consider
getting one of the new improved and more performent yet low cost M Series devices.
Hope this helps.

HP4275A can not pass self test after running the labview program

I am using Labview to control HP4275A LCR meter. The Labview program is just the instrument driver for the HP4275A, and it works great. Before running the program, the instrument can pass both Open and Short test perfectly. But after running the program, it can not pass self test, neither Open nor Short. I don't know why?? Is it relative to my Labview program??
Thanks

Thank you so much for your help. Yes, the instrument is in Local after running the instrument driver. In normal Open self test, just choose Capactiance as the Display A, and leave the four output terminals open then press the Self Test button. The Open self test will start and "OP" will be shown in the DIsplay A window, after 2 seconds, the open test will be finished. If something abnormal, the number of the abnormal step is displayed in Display A. Similar with the Short test.
The problem I had was: before running the instrument driver, the self tests pass; but after running the instrument driver, the Open and Short test show abnormal, Open test is abnormal at step 17, and Short test is abnormal at step 24.
And the instrument driver is only write commands into the instrument and then read back measuring values from it. Nothing else. So I am not sure if the problem is my instrument driver.
The weird thing is the problems happened several times and then if I do the Open and Short self test again after running the instrument driver, both pass. I am not sure whether the problem will come back or not.
Ia there any help??
Big thanks

DAQCard-6024E Card Fails Self Test - what wrong?

I am attempting to write a Visual C++ application that uses a DACCard-6024E and I have installed the NI-DAQmx 7.4 drivers. Measurement and Automation Explorer has detected the card as "Dev1". An I/O port and IRQ were assigned.
When I do a "Self-Test", I get the following error message.
Error
The device self test has failed. The error report from the device driver is as follows:
Error -200020 occurred at Self Test
Possible Reason(s):
Self-test of the device has failed.
OK
Am I missing a step that will enable the board?
Thanks.

Try removing the device from your PC, then uninstall your DAQmx drivers and install DAQmx 8. Shutdown and put the device back in and see if it passes self-test.
Michael P
National Instruments

Ipod nano starts with a self-test after sleep

My new Ipod nano runs a kind of self-test if it was at sleep for a couple of hours.
Does this have to be? If not how can I determine specifically what is wrong? Thanks

Gert,
When iPods are not used for a period of 24 hours of more then they go into something called "Sleep Mode" or "Deep Sleep".
You'll see the Apple logo when you try to turn your Nano back on which is normal, you are "waking up" the iPod.
I've never heard or seen of such self-test, is it still on self-test? Or you want suggestions on how to get out of that?

LMS 2.6 Self Test database.pl fail

Hi,
We had a server crash and when I brought it back up, LMS is having some issues. I imagine this is due to the database not being shut down cleanly. I did a self test and got the message below. I've tried restarting dmgtd but no dice. LMS 2.6 is running on a Solaris 9. Any assistance with this is greatly appreciated. Thanks!
database.pl
FAIL Self Test Fail to query dfmInv.DbVersion, Error: Database server not found (DBD: login failed)
Self Test Fail to query dfmInv.SYSTABLE, Error: Database server not found (DBD: login failed)
Tim

Thanks for the info.
I ended up doing complete restore with the LMS restore process. Everything appeared to work fine, but now I'm having some major issues with DFM. None of the alerts are clearing (manually or otherwise), devices are stuck in a Learning state at 10%, and I'm getting some weird errors in dmgtd.log during startup. I'm getting several alerts about EssMonitor and jrm similar to the ones below.
#2107:TYPE=WARNING:The daemon manager cannot find dependency EssMonitor for EPMServer. Message ignored
#2107:TYPE=WARNING:The daemon manager cannot find dependency jrm for DataPurge. Message ignored.
If you have any ideas about this, I would appreciate the input.
Tim

Hard Drive failed both postive read and smart short self test

Hello, my Lenovo Think Pad's Hard Drive failed both targeted read test (error code WHD20-HJF) and the smart self test (error code WHD16-KPY). I admit that I'm an older user and I have no idea what this means and what is the possible fix for it.
I am open to all suggestions;
THANKS,
Octavious ONeal

Hi, Octavious
When the hard drive fails those tests, it's an indication that the drive is dying. It's recommended to back up any valuble data on the hard drive and then replace it soon. The drive may still work for a little while, but it will likely stop working sometime soon.
Hope it helps,
Adam
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution!" This will help the rest of the community with similar issues identify the verified solution and benefit from it.

HDD replaced with SSDHDD & Drive Self Test failed hardware scan by LSC

Hello! Happy new year!
I bought a new SDDHDD instead of the HDD that came with the laptop when I bought it because it was faulty.
I want to make sure that the new drive isn't faulty when running the hardware scan using Lenovo Solution Center (LSC), I got this result code: WHD01V000-HK9V1D - Warning for the SMART Drive Self Test. However I tried testing using HD Sentinel and SeaTools but they showed no errors.
Note: I'm taking LSC seriously because it showed warnings then critical alerts before my first HDD failed so I don't want to ignore it.
Please let me know what it means and if I should worry or how to fix the problem? Or does it simply not support SDD?
Thanks for reading this long message! (Sorry)

Hi, quocphong
It sounds like the hard drive is running okay overall, but it has some bad sectors in it. You will not be able to read or write to these sectors. That being said, I would first try running a ChkDsk on the hard drive and see if any of the sectors can be repaired. To run a ChkDsk, go to Computer and right-click on the C: drive and select Properties. Navigate to the Tools tab and select the box that says Check now... This should scan the drive for errors and attempt to fix them if possible. The test can take a while, so I would do it when you will not need access to your computer.
If the test is not able to fix the errors, then I would contact Lenovo at 120-11072 (Toll Free) or +(84) 8 3521 8000 (Standard Charges Apply) and discuss a hard drive replacement with them. As for Windows, you will need to ask for recovery discs as well. Lastly, I would backup everything on the current hard drive so that it is not lost.
Hope it helps,
Adam
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution!" This will help the rest of the community with similar issues identify the verified solution and benefit from it.

Printer failure after self-test .Deskjet 3650

hp deskjet 3650 printer failure. This happened after running a self-test to check ink level. Oddly, the test report printed out OK. I used the "lift cover 4 times" method to do the test

I have the same problem, starting 2 weeks ago.
I tried the suggestions at http://www.hp.com/support.
None of them worked.
Their advice in this case is: The product needs service.
Following this link, they checked my serial number and found that the printer was out of warranty.
They then displayed the message: The following services are available to you. Please choose ONE of the following:
You guessed it - there were no services available to me!
So what I am hoping is that someone can tell us how to fix it ourselves.

Can't Create a Data Source - Failed to test connection. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied

Hi there,
I am having a serious issue with The Power BI Data Management Gateway which I am hoping that someone can help me with.
Basically I am setting a connection between a Power BI demo site and a SQL 2012 Database based on Azure. The Data Management Gateway and is up and running, and Power BI has managed to connect to it successfuly.
By following the tutorials at
here I was able to successful create my Data Connection Gateway with a self-signed certificate.
However, when trying to create the data source I come into problems. The Data Source Manager manages to successfully resolve the hostname, as per the screenshot below:
Bear in mind that I exposed the require ports in Azure as endpoints and I managed to modify my hosts file on my local machine so I could access the SQL server hosted in Azure using its internal name -- otherwise I would not be able to get this far.
However the creation of the data source also fails when trying to created it whilst logged in the SQL server in question:
The Data Source Manager returns the error when using the Microsoft OLE DB Provider for SQL Server:
Failed to test connection. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
I tried using the SQL Server Native Client 11.0 instead but I also get an error. This time the error is:
Failed to test connection. Login timeout expiredA network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.Named Pipes Provider: Could not open a connection to SQL Server [53].
Some considerations
If I provide an invalid username/password, the Data Source Manager does say that the username and password is incorrect.
Firewall is turned off in the SQL Server (either way, this error also happens if I try top use the Data Source Manager whilst logged in the SQL Server itself).
SQL Profiler does not show any attempt of connection.
The SQL server instance in question is the default one.
The error happens regardless if I select the option to encrypt connection or not.
In SQL Configuration manager I can see that all protocols are enabled (TCP/IP, Named Pipes and Shared Memory.
The Event Viewer does not provide any further errors than the one I have copied in this post.
I'm at a loss here. Could someone please advise what might I be doing wrong?
Regards,
P.

Here is what I had to do to solve this issue:
Basically I had to add the MSSQL TCP/IP port as an end-point in Azure. After I did that, then I was able to create the data-source. However, I was only able to authenticate with a SQL account, as any domain account would return me an error saying that the
domain isn't trusted.
What puzzles me here is how come the Data Source Manager would inform me that an account username/password was invalid, but it would fail/timeout if I provided valid credentials (!?!?!!?)

G4 Quicksilver failing to startup after chime

My usually stable 10 year old G4 hard drive (attached to VGA monitor) is having serious problems with it's starting up process, so I am presently nursing it along (without shutting down at the end of the day) by using sleep mode. If I shut it down, chances are it fails to power up again. When I press the power on button to startup, I hear the chime and the startup process as usual, then everything stops within seconds, before the monitor screen is due to come on. The two external devices attached are the keyboard with mouse, plus a USB hub. No recent upgrades or changes. Everything is backed up on an external firewire disk. Since this trouble started a few days ago I have replaced the lithum battery and managed to successfully start it up only once (after a number of attempts) so I can nurse it along. I have tried all the usual troublshooting - when I restart in either safe, verbose, or reboot off OSX CD, single user mode, extensions off, or try to reset the PRAM fails to chime twice - in every instance it won't get past the chime. Checking the system profiler 'power on self test' indicates 'failed', failure type is 'external cache'. As I can't reboot off the OSX10 or systemworks CD I can't run Diskwarrior on the operating system or reinstall the operating system. So, I am now at the limit of my capabilities.
Can anyone tell me what the problem is?
Frances

The "external cache" would be referring to the L3 cache chips on the processor board.
That error does not bode well for future longevity.
It isn't that uncommon for the L3 to fail on that processor, most likely due to the hot-blooded nature of the dual 1 GHz machine.
It is likely time to search for a used processor daughter card (eBay).
It may also be possible to disable the cache using CHUD from the Developer tools in OS X.
Depending on the exact type of failure, this may (or may not) return some reliability in the boot process.

865PE NEO2 FSIR fails memory tests

This is the second MB that I've had this problem with, so something is causing them to fail. Here's the story:
New install, 865PE Neo2 FSIR + P4 2.6GHz 800MHz FSB, 2 x Crucial PC3200 256MB DDR, everything seems ok, XP installs with no problems.
About a month down the road I'm plagued by sudden reboots, Microsoft Error Reporting says RAM, says to DL and run it's DOS memory check utility. I get the utility, create bootable CD and run the utility, computer fails all RAM checks. I pull each RAM stick in turn and re-run the check with each stick separately, still fails all tests. Shortly after this, the board refuses to POST. Ship the board back to New Egg for replacement.
Installed replacement MB with 4 x 256MB Crucial PC3200, Microsoft DOS memory check program passes, no problems. About 2 weeks later I run into minor instability so I run the same memory check again, the board fails all tests????? I pull all Crucial memory sticks and put in a test stick of Corsair XMS 3200; same result, failure of all memory tests.
At this point, WinXP still runs, but this is the same pattern that the other board showed, right until it quit altogether.
It occurs to me that I DID flash BIOS to 1.9 between the time I first tested the RAM and got a pass and the time I tested and got a failure, could this be a coincidence? I can't remember if I updated the BIOS on the first board or not, so this may mean nothing.
System Specs:
MSI 865PE NEO2 FSIR
P4 2.6GHz, 800MHz FSB (all defaults, no overclock, Vantec HS)
Crucial CT3264Z40B.8T PC3200, CL3 256MB (2 Modules)
Crucial CT3264Z40B.8T2 PC 3200, CL3 256MB (2 Modules)
(Tested with same results with single Corsair CMX512-3200C2PT 512MB)
Antex True Power 430W PS
ATI Radeon 9600 Pro
All PCI slots open
Seagate 120GB System drive, 7,200RPM primary master
IBM 30GB drive, 7,200RPM primary slave
LiteOn DVD ROM secondary master
Sony CDRW secondary slave
2 x IBM 30GB drives on Promise PATA.
I know I'm probably gonna have to RMA this board, but I'd really like to know what is causing this so I can avoid it next time.
If anyone has any ideas I'd sure appreciate it.
Scott

Quote
Originally posted by jwspicer
As they say - been there, done that. Always flash using DOS, and always keep backup, so I went back to the original BIOS for the board. No luck. Apparently once the screwup is done - it stays that way.
--BUT--
Suspect it is the reallocation for the P4 EE that is the issue. Reason is that Memtest86 has been running on that box for 9 hours now with NO error. However, it also shows only 104K of reserved memory. My other 865 board with onboard RAID (an ASUS P4P800 Deluxe) shows 687K reserved. So either the ASUS is wasting a lot of space, or the MIS is no longer correctly indicating the amount of memory reserved by the BIOS (including the Promise BIOS) at startup. Then Microsoft's utility is not correctly scanning. But Memtest, which probes for the "correct" setting, is. (The Memtest86 version is 3.0, and the test was done with the Promise enabled and drives attached (so the BIOS loads) and all the other setup was as it would be normally (standard IBOS options, etc.)
So who's right? And if MS' tool has the problem, does that indicate Windows XP reads memory the same way? Hmmm...
Hmm, I haven't tried reverting BIOS, but I'm typing this on the affected machine (which Memtest 86 says is fine) with only the two RAM chips it likes and so far no problems; I've run PCMark4 and 3DMark4 benchmarks all night and no problems, it was still happily churning away on 3DMark this morning. I guess either one of the Crucial sticks it doesn't like is bad or Crucial changed something in a revision to the chips it doesn't like.
Just a FYI, the Crucial sticks it DOESN'T like are CT3264Z40B.8T2
The sticks it DOES like (at slow or fast performance, forget about turbo or ultra turbo) are CT3264Z40B.8T
Both pairs are PC3200, CL3, 256MB DIMM's, single sided.
I think you're right about Microsoft's RAM tester being buggy, I can't believe ANYTHING could run if the RAM was actually giving the errors it shows, EVERY test shows things like "expected result 11111111 actual result ff1e0001" The Microsoft tester does run fine on the other 5 computers here; a mix of laptops and desktops; none using this board. It also ran on this board when it was installed, I guess the BIOS upgrade must be the cause.
Scott

Software Updates for Remote PXI System/DAQ-mx Self Test

1) In MAX, I'm attempting to run the Labview Realtime Software Installation Wizard. When I select the software for install, I get an error "Cannot Process Install because other Dependencies are required: Labview RT 7.1.1". What should I do to correct the problem? I'm trying to update both DAQMx and Traditional DAQ from 7.2 to 7.3. The wizard actually indicates that the remote system only has 7.2, and that it sees that 7.3 is available.
2) Also in MAX in the Remote System Tree, I get an error when trying to perform a self test on my PXI-6025 card, or when I attempt to reset it. The error code is 88705. I noticed on another post that there might be the need to perform a repair of the installation. This was done for both DAQMx and Tranditional DAQ, neither of which fixed the problem.
3) In MAX I have used the Tools>>Traditional NI-DAQ Configuration>>Remote DAQ Configuration to configure my PXI-6025 DAQ channels, accessory, device #, etc. I then proceed to run a Analog Input VI on the remote system by correctly targeting it and selecting i.e. channel 0. No errors occur. However when I try and select "Browse" under the channel control, the "Select Names" window pops up empty. I would assume that this window would pop up with the DAQ channel names assigned during the channel configuration of the PX-6025??? Whats missing here?
Thanks
Pete.

Hi Pete,
I'm assuming you are using LabVIEW RT 7.1, since that is a requirement for using DAQmx. Here are my responses for your three issues:
1) You are correct in assuming you can upgrade the DAQ drivers in the manner you outlined, normally that works fine. However, as the following KnowledgeBase points out, the list of dependencies vary for different installs.
http://digital.ni.com/public.nsf/websearch/F5D80FBE806B4B9D86256F0F005630CF?OpenDocument
Do you have LabVIEW RT 7.1.1 installed, which appears to be the required dependency? If not, you may download this from ni.com>>Drivers and Updates
http://digital.ni.com/softlib.nsf/MainPage?ReadForm&node=132010_US
If so, but the problem persists, please post all versions of your software so I can determine where the incompatibility lies.
2) After we take care of upgrading the DAQ drivers, let's see if the 88705 error goes away, it might take care of it.
3) Again, all the steps you described are correct. It might be that all these problems are related and due to a bad install of NI-DAQ.
When a number of software issues like this arise all at once, it might be best to just re-format the controller and perform a fresh install of everything. Often times that will correct the erroneous behavior.
Regards,
Jeff M.
Applications Engineering
National Instruments

PI 7.1 components fail self test after SP7 application

Similar Messages

Maybe you are looking for