Deploying teststand V3 - mdac98 error on target machine

Thank you in advance.
I have two PXI computer that I'll like to deploy sequence file to, from a development machine, I have successfully create the installer using tool>>deploy test stand system but I get error message "mdac98" required when I attempt to install it to win98 target machine. I have been to the windows website to download and install "mdac98.exe" but I still get the error.
I have read some literature on this issue but got no where. Out of curiosity what is the different between "disturbing test stand" and "deploying test stand". anyone?

Rash,
I just answered a question you posted on DCOM that was nearly identical. Are you also having problems with mdac or was this question supposed to be on DCOM?

Similar Messages

Crystal report error on Target Machine

We have to provide application exe to our clients. The application is developed in Visual Studio.Net 2010 and by using SAP crystal report CRforVS_13_0. Client must be able to fire reports on their target machine on which the Dot Net framework and u201CCRforVS_redist_install_64bit_13_0_1u201C run time utility is installed. But it gives a crystal report error on the target machine.
Our development and target machines have Win 7 Professional, 64-bit OS installed.
Kindly provide us with an appropriate run time version for target machine in order to fire reports or any other solution in order to make our project work on target machine.
Thanks!

Thanks a lot Don for your valuable suggestions.
We have already taken care of the points which you mentioned in your reply on development side. Also, we have downloaded crystal report from the link which you posted but on DEPLOYMENT side we are unable to run reports from our application.
It gives the notification when we try to install crystal report on a target machine as "You must have visual studio 2010 installed in order to install the crystal report".
The DEPLOYMENT problem we are facing is in RUNTIME environment on TARGET machine. Our TRAGET machine has properly installed Win 7 Professional 64 bit, .NET Framework Ver 4 and CRforVS_redist_install_64bit_13_0_1 . We also have properly installed application on this machine. We got no errors while installing any of the above. The problem starts when we fire a report on target machine from the application.
We get the error as "The type initializer for 'CrystalDecisions.CrystalReports.Engine.ReportDocument' threw an exception"
So, we are looking for an appropriate RUN TIME version of Crystal Report which can be installed on the target machine to fire reports (where visual studio 2010 is not installed).
Please help suggest an exact version to download for target machine and the steps if it has a specific procedure.
Thank you!
Ruchir

MDT not proceeding to Deployment Wizard after entering credentials on target machine

I have a server configured with MDT 2012 and am using WDS on another server with DHCP and AD to push that out to client machines. Sometimes it works, other times I enter the network credentials into the wizard on the deployment client and instead of saying
'Processing Rules: Default' and proceeding to the task sequence selection, it says 'Initialization Complete'. The window then disappears leaving just the Solution Accelerators background.

Hi,
Please check the logs referred in the following article:
http://blogs.technet.com/b/askcore/archive/2012/05/08/mdt-2010-amp-2012-my-deployment-failed-what-and-where-are-logs-i-should-review.aspx

I have followed the steps for running exe on target machine but camera streaming did not found yet.

Install the following run-time engines:
LabVIEW Run-time Engine (same version that was used to develop the VI)
Vision Run-time Engine (same version that was used to develop the VI)
A single-seat Vision Deployment License is required for each target machine on which you install the Vision Run-time Engine. See Related Links for more details.
Copy the following DLLs from your development machine's System Directory, typically C:\Windows\system32, to your target machine's System Directory.
ImaqDirectShowDll.dll
ImaqDirectShowExport.dll
Register ImaqDirectShowExport.dll by selecting the Windows Start Menu and selecting Run.
Type in regsvr32 C:\WINDOWS\system32\ImaqDirectShowExport.dll and click OK to register the DLL.
If you are on a different OS or if the system directory is different and you want to copy the file path instead of typing the whole path, you can drag the file to the command line in the Run prompt, highlight the path, right-click and select Copy.
Paste in the command prompt window by right-clicking and selecting Paste.
The ImaqDirectShowDll does not have to be registered.
I have followed all above steps ,
Can any one help me for solution ?

My guess is that the driver is missing at the target system.
You can add the driver (part of Vision Acquisition Software) you need (IMAQ, IMAQdx, ..) under the Additional Installers Section of your Build Specification and you will also need a runtime license.
Christian

Why doesn't my TestStand deployment installation show up under my Windows start menu of my target machine?

Why doesn't my TestStand deployment installation show up under my Windows start menu of my target machine?
I have successfully installed working deployments to target machines. However, I was expecting to see the installation listed as "My TestStand System A" in my start menu, but it is not. Am I misunderstanding something here?
Also, if I peform a different second deployment to the target station like "My TestStand System B", all of the LabVIEW files from my previous installation for "My TestStand System A" disappear from the target directory (c:\Program Files\My TestStand System A).
I am using TestStand 4.2.1 Professional on the development station with Windows XP and LabVIEW 2009.
Solved!
Go to Solution.

Thanks Paul,
That solved my second problem and inspired me to search deeper for the answer to my first problem. The answer is in the "Distributed Files" tab, "installer properties", "Create a Program Item" checkbox:
Wouldn't it be nice if this was automatically checked by default for the main sequence files? Wouldn't it also be nice if "Upgrade Code" was automatically regenerated by default whenever we saved the *.tsd file under a different name?
Thanks again,
Eugene
Message Edited by Eugene12 on 05-06-2010 04:27 PM

Can a TestStand deployment built with XP run on a target machine running Windows7?

All,
I knew it would come to this eventually. My very reliable development machine is running Windows XP. I am now facing the situation of building a TestStand deployment to distribute to target machines that are running Windows7. I am trying to head off trouble and troubleshooting that may not be worth it. Will this work?
Thanks in advance for any information regarding this situation.
Troy

Hi Troy,
You shouldn't run into trouble, but you may want to be aware of the differences in directory paths.
Cheers,
KyleP
Applications Engineer
National Instruments

ActiveX Automation server error on deployed TestStand

I'm trying to deploy TestSTand 2.0 + LabVIEW 6.1 on a PC under Win-2K.
I created and deployed TS Engine and Operator Interface for LV.
I try to deploy the "Auto.seq" test from the TS exemples.
Of course, it works on my Development system.
On the deployed system, I got an error : -18351; An error occurred reading an ActiveX Automation server type library.
Step 'Read Database Option - Construct' of sequence 'Get Database Options' in 'SequentialModel.seq'
Step 'Read Database Option - Read Options' of sequence 'Get Database Options' in 'SequentialModel.seq'
After having ignored those 2 errors, the tests goes on normally and the report looks fine.
I also get this error opening the database configuration:
Step 'Read Database Option - Construct' of sequence 'Edit Database Options' in 'Database.seq'
From answers already given for similar subjects, I've checked that TsDBOptions.dll is present and registered (done regsvr32...) on the PC.
Can someone help ?
Note: upgrading to more recent TS + LV versions is not a solution!

Whether you are using database logging or not, you should not get an error like that when database options are loaded. From the kb's you specified it sounds like there was an issue with a COM/ActiveX server not getting registered in the past. Especially on machines in which TestStand was installed from a deployment rather than the main installer. Have you tried running the version switcher like the KB suggested? Did it succeed or give an error? If it gave an error what was the error? Could you perhaps try a fresh install of TestStand on a clean machine?
-Doug

Not able to deploy windows kernel driver on target machine from visual studio

I have created windows kernel driver, and signed it with production certificate. Now I could install this driver on my target machine manually(copying inf, cat and sys).
I want to make use of the visual studio 2013's deployment facility to deploy the driver automatically. But when I try to add the target computer(with administrative account) it failed with error message "The account credentials used to connect to the
target computer could not gain administrator access to the target computer. Try using the built-in Administrator account".
what possibly could be wrong?

Pavel The host machine is on a domain(say ABC) and I am logged In as the domain administrator. On The target machine I am logged in as the local administrator. Now while adding the target computer from visual studio I am asked for the administrator account
credentials and I am providing the local administrator credentials there.
Pavel I found it is necessary to install "WDK Test Target Setup x64-x64_en-us.msi" on the target machine which I had not run. Once installing that I passed through the previously mentioned steps and after performing few installations target machine
got rebooted. And then the deployment process hanged on step a "Attempting to connect...". Tried this for multiple times but result in to the same problem.

Help with x64: fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'

Hello, I am trying to complie some C code for some applications I am working on in labview (I am using Labview 2012 64bit).
When I try to build my code in Visual C++ 2010 ( I have set it up to be able to use x64) I get the following fatal error:
nivision.lib(StartupShutdown.obj) : fatal error LNK1112: module machine type 'X86' conflicts with target machine type 'x64'
Which I understand that .lib does not have a 64bit compatability. However, if I were to use 32bit code, how can I link/emulate it to my 64bit labview? Is there a good tutorial on this application? The problem is the rest of my application uses and requires 64bit labview, so I am stuck in this enviroment.
Thanks.

dbrittain wrote:
Thanks for the reply. The C code I have cross correlates images, and it does reference the image inputs and size variables from the nivision classes. I am thinking of using a side by side labview environment with shared variables. I have not done this before, do you have any good examples? Can you make the library function node a shared variable or only the elements within it?
I guess I could try to convert to labview, but the are a lot of lines of code that I would prefer not to try to wrap my head around in translation.
The LabVIEW API in Vision Development Module has functions that let you get access to all those parameters as well as the raw image data pointer. A common design is to query those items on the LabVIEW diagram and then pass them to your DLL. This would mean you wouldn't need to make any calls into the Vision DLL from your C code.
As for examples showing how to use shared variables, keep in mind that it isn't just like doing a function call. The more appropriate way to think of it would be communicating with another VI by getting and setting controls and indicators while it runs. You could put all your arguments into a shared variable and set a boolean indicating it is ready, then wait for another boolean to go high indicating the other code has finished and placed its results in another shared variable. Your application code interacts with the shared variables just like a control/indicator/local variable. This of course is a simple description and I would not be surprised if there are well-defined frameworks/examples searchable in the forums that use shared variables in this manner.
Eric
Eric

Error Message SCCM 2012 ERROR: Unable to access target machine for request

Should I be concerned with this message, or will it resolve on its own?
---> ERROR: Unable to access target machine for request: "2097153953", machine name: "MININT-NAEAFL", access denied or invalid network path. SMS_CLIENT_CONFIG_MANAGER 4/21/2015 11:34:59 AM 8100 (0x1FA4)
Execute query exec [sp_CP_SetLastErrorCode] 2097153953, 53 SMS_CLIENT_CONFIG_MANAGER 4/21/2015 11:34:59 AM 8100 (0x1FA4)
This machine is nowhere in my AD or SCCM...It was at one time, But I have deleted it. It still appears in the Logs. The CCM.LOG to be Precise
Bryan

No, this is nothing to be concerned with. Assuming you have auto-client push enabled, it will try to push the client agent to a resource without the agent every hour for 7 days. Thus, after the 7 day period expires from the last time it was discovered,
it won't try to push to this system anymore.
Jason | http://blog.configmgrftw.com | @jasonsandys

Deploy TestStand System error

When I try to run:
Tools>>Deploy TestStand System>>Deployed Files>>LabVIEW Options>>Lock VI Diagrams
I get the following error after I hit the Build key:
Failure : linker.cpp line 2022
LabVIEW version 6.1
I suspect I need version 7.0?? Can anyone confirm this or let me know what I'm doing wrong?

Rick,
I've only got one simple vi in my sequence. I can run the build utility with no errors until I select the "Lock VI Diagrams" option. Note that my error code is now 1035 instead of 2022 like it was previously. The 2022 error was caused by not suppling password in the Lock VI Diagram box.
Error Code:1035
Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Invoke Node in TestStand - Dist Chg and Save VIs.vi->TestStand - Dist Build LLB Image.vi->TestStand - Build VI Distribution.vi->TestStand - Build VI Distribution AX Wrapper.vi->TestStand - Build VI Distribution AX Wrapper.vi.ProxyCaller
Attachments:
deployment_trial.zip ‏14 KB

Provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.

hi all,
i want to connect to server side from client , i am using sql server 2008 sp1 and os winn 7 64 bit, but it give me an error as above.
also i tried this link:
http://social.msdn.microsoft.com/Forums/sqlserver/es-ES/c0481462-fedf-4f3b-b984-ae3fef64a3b1/provider-tcp-provider-error-0-no-connection-could-be-made-because-the-target-machine-actively?forum=sqldatabaseengine
and i configured two things as follow:
windows firewall --> port --> spacial local (1433) --> allow the connection -->public (checked) and sql server network configuration manager -->protocols for mssqlserver TCP/IP(enabled).
note: my client and server windows firewalls is disabled.
but i can not solve this issue.
pls help me.
thanks & best regards.
pls help me

hi Sathish,
thank you,
this is my connection string>>
"Data Source=192.168.1.106.1433;Network Library=DBMSSOCN;" +
"Initial Catalog=rasol;Integrated Security=sspi;"
And I tried into command prompt, it replied for 192.168.1.106.
best regards.

Deploy teststand system Labview instrument drivers

I'm trying to deploy a teststand application but I have an error with some Labview VI's.
I'm using some VI's to control an Agilent 34401A, so Labview instruments library that
is in the default package was used. The error says that Labiew Could no open the following VIs...
I don't want to install the Labview development system on the target machine, so I don't know
how to fix this problem.
I tried to copy the library to a different location an removing the VIs that are not wired (VI Tree.vi),
but I have the same error. (On the sequence was changed the path to the new VI location).
Thanks
Marcos

Marcos,
You can execute VIs using the LabVIEW Runtime Engine, but all of the source VIs must be processed to collect their required dependencies and insure they are compiled in the current version of LabVIEW. The Deployment Utility process VIs from your sequences automatically. The TestStand Reference Manual has a chapter on deploying TestStand systems that should help you get started.
-Rick Francis

Deploying TestStand

I am trying to use the Deployment Utility to deploy TestStand to a target. I have modified the TestExec.prj through CVI and have created an installer using CVI to do that. I have also modified the modelsupport2.prj with some additional GUI's. I have also made the necessary changes to all the other files required. I have sone this several times with other versions of TestStand.
For some reason, the deployment utility is not picking up the files located in /All Users/Documents/TestStand 4.1.1/Components/
Therefore it is not getting the modified GUI, the Language files requires, the modelsupport2 files, etc. etc. etc.
I have tried multiple deployments selecting different settings, but nothing seems to work. I finally copied iver the components directory from the development machine to the target and now my modelPanels GUI (which is all modifed in modelsupport2.dll) and it seems to work. However, this is not the correct way, right????
Please advise.

Hi Kelly,
All the files that were modifed in the modelsupport2.dll have been modified in the TestStand public directories, so I know that is not the problem. The files in the normal TestStand directories remain unchanged.
I have also tried to select the "Display files in the TestStand Public Directories", but this is where I run into other problems. The deployment utility reports several errors and warnings that will cause my deployment to fail. The errors reported are as follows:
1. You may need to add any sequence files referenced by the following expressions: (Too many to list, but all have to do with reportgen)
2. The following files were not found: (too many to list, but all are .vi's. I don't even have LabView installed!)
3. The following vi's could not be loaded: (Again, too may to list, but see above.... Labview not installed!)
Regarding the vi's, I have tried to deselect any of the items that seem to be LabView related, but It still gives me those errors/warnings. I have also tried to exclude any LabView items by excluding them in the Labview sections, but that does not help either.
Please explain if possible.
Thanks,
Gregg

PXE boot no longer working - blank cmd windows shown. If run Scripts/Litetouch file from target machine wizards runs as expected??

Hi, My MDT server no longer works as expected via PXE boot. After the target machine loads the .wim file an empty command windows is shown. I have returned the custom settings.ini and bootstrap files to default and ensured nothing is being skipped within
the task sequence within both files in hope of viewing the wizard.
However from the same target machine if I map drive to my Deploymentshare/Scripts directory and run LiteTouch file I am asked for domain credentials and the Deployment wizard is displayed asking for task sequence to be selected.
I believe this error is a result of two things:
1) I applied some windows updates to my mdt server (running on 2008 r2).
2) I was implementing changes to
ZTIWindowsUpdate.wsf which i have now returned to default settings.
I have also regenerated boot images and re added to WDS.
Any help much appreciated?
Regards,
Paul

Hi Paul,
This sounds familiar; I only encounter this behaviour with certain kinds of laptops (Latitude E65x0) but I usually just provide the "wpeutil reboot" command in the empty command window to keep things going. All other hardware is deployed with the
same task sequence and this behaviour does not occur anywhere else...
A bit obvious maybe, but did you check if there is still a "Next Phase" step present and enabled following directly after the "Install Operating System" step?

Deploying teststand V3 - mdac98 error on target machine

Similar Messages

Maybe you are looking for