Updating Stalled Process Post ES2 Upgrade

I just upgraded our server from 8.2 to ES2 SP2. I had several active process instances before the upgrade that I'm testing post upgrade.
The process I'm testing uses a Query Single Row Operation which is stalling. It's stalling because I don't have a required parameter(Data Mapping) defined. This parameter was not required in 8.2 so it worked fine.
So I fixed that issue with the process(after creating an application and importing the process), and attempted a retry on the process, but that is not working. Livecycle continues to use the invalid version of the process that does not specify the required parameter when I attempt a retry.
So, my question is how can I update the "active" version of the upgraded process and retry the stalled process instances?

The "deploy" option in the application version menu is apparently what I was looking for.

Similar Messages

I Have Update Iphone4 to version 6.1.3 , I have inserted Airtel sim post the upgrade its showing as "NO SERVICE" , Contacted Apple support desk only to find that phone is Locked with AT

I Have Update iphone 4 to version 6.1.3 , Post the upgrade have tried inserting airtel sim card only to find as NoService .
Tried calling Apple support desk later came to know that my phone is locked my AT&T. Could some one help me unlocking the Phone and let me the cost in India.
However, tired submitting the online AT&T form to unlock it , its asking for SSN number which my friend from US got phone which I don't have(SSN).
Could some one help me .
Thanks
Panka Kumar

ONLY AT&T can authorize unlocking it. If you are trying to fill out the on-line form, make sure you choose non-customer. That, or have your friend submit the unlock request. If you are not a customer, you will have to provide proof of purchase for a no-commitment phone from either Apple, or directly from AT&T, which you obviously do not have.

Exporting a ES 8.2 Process in ES2 9

Is there any way to export and migrate an ES version process in ES2? When I try to create an LCA, I'm getting a message that states "The LCA can't be created due to the selected applications contain 41 imported legacy resources as below that still have deployment IDs."
I understand what legacy deployment are, but I don't want to upgrade these processes to ES2 compatible yet. I have to be able to make updates to this processes in prod as the upgrade created incompatibilities that have to be addressed.

Jasmin
Thanks as usual. That helped me to find the "Create a Livecycle archive from the selected components" button.
PS. Please take a look at the upgrade issue that I posted in the Livecycle installation forum.

Launched software update on MacBook v. 10.5.8 during restart, update stalled now nothing will launch-quits unexpectedly. Help!

Launched software update on MacBook v. 10.5.8 during restart, update stalled now nothing will launch-quits unexpectedly. Help!

As long as the report ends up with 'Permissions repair complete' then, as far as permissions go, you are fine. You can ignore the various statements in the report:
Permissions you can ignore on 10.5 onwards:
http://support.apple.com/kb/TS1448
Some general advice on updating Leopard:
It is worth noting that it is an extreme rarity for updates to cause upsets to your system, as they have all been extensively beta-tested, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first to an external hard disk. Ideally you should always have a bootable clone of your system that enables you to revert to the previous pre-update state.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO update from the Apple download site.
The Combo updater of Leopard 10.5.8 can be found here:
http://support.apple.com/downloads/Mac_OS_X_10_5_8_Combo_Update
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Full details about the 10.5.8 update here: http://support.apple.com/kb/HT3606
More information on using Software Updater here:
http://support.apple.com/kb/TA24901?viewlocale=en_US
Using the Combo updater ensures that all system files changed since the original 10.5.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.5.7 to 10.5.8. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications and turn off energy saving and screensaver.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious! In fact a second restart can be recommended.
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them compliant with the latest version of your operating system. Give them a week or two while you regularly check their websites for updates.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
[b]If you are updating Safari (or just have):[/b]
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed an OS update and Safari is crashing, the very [i]first[/i] thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party add-on.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692
To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
Again, the advice is to remove all Input Managers from the following directories:
/Library/InputManagers
~/Library/InputManagers
especially prior to system updates (they can always be added back one-by-one later).
Solutions for troubleshooting installation, startup, and login issues in Mac OS X v10.5
http://support.apple.com/kb/TS1541?viewlocale=en_US

HT3606 Mac OS X v10.5.8 Combined Update stalls updating my G4 1.25

Mac OS X v10.5.8 Update stalls updating my G4 1.25. A peek at the files being installed was reference to "standalone i386 efi" which has no place on a PPC. Are there different versions of the combined update? There are different sizes of the combined update.

Some general advice on updating Leopard:
It is worth noting that it is an extreme rarity for updates to cause upsets to your system, as they have all been extensively beta-tested, but they may well reveal pre-existing ones, particularly those of which you may have been unaware. If you are actually aware of any glitches, make sure they are fixed before proceeding further.
So before you do anything else:
If you can, make a full backup first to an external hard disk. Ideally you should always have a bootable clone of your system that enables you to revert to the previous pre-update state.
Turn off sleep mode for both screen and hard disk.
Disconnect all peripherals except your keyboard and mouse.
1. Repair Permissions (in Disk Utility)
2. Verify the state of your hard disk using Disk Utility. If any faults are reported, restart from your install disk (holding down the C key), go to Disk Utility, and repair your startup disk. Restart again to get back to your startup disk.
At least you can now be reasonably certain that your system does not contain any obvious faults that might cause an update/upgrade to fail.
3. Download the correct version of the COMBO update from the Apple download site.
The Combo updater of Leopard 10.5.8 can be found here:
http://support.apple.com/downloads/Mac_OS_X_10_5_8_Combo_Update
If you prefer to download updates via Software Update in the Apple menu (which would ensure that the correct version for your Mac was being downloaded), it is not recommended to allow SU to install major (or even minor) updates automatically. Set Software Update to just download the updater without immediately installing it. There is always the possibility that the combined download and install (which can be a lengthy process) might be interrupted by a power outage or your cat walking across the keyboard, and an interrupted install will almost certainly cause havoc. Once it is downloaded, you can install at a time that suits you. You should make a backup copy of the updater on a CD in case you ever need a reinstall.
Full details about the 10.5.8 update here: http://support.apple.com/kb/HT3606
More information on using Software Updater here:
http://support.apple.com/kb/TA24901?viewlocale=en_US
Using the Combo updater ensures that all system files changed since the original 10.5.0 are included, and any that may have been missed out or subsequently damaged will be repaired. The Delta updater, although a temptingly smaller download, only takes you from the previous version to the new one, i.e. for example from 10.5.7 to 10.5.8. Software Update will generally download the Delta updater only. The preferable Combo updater needs to be downloaded from Apple's download site.
Now proceed as follows:
4. Close all applications and turn off energy saving and screensaver.
5. Unplug all peripherals except your keyboard and mouse.
6. Install the update/upgrade. Do not under any circumstances interrupt this procedure. Do not do anything else on your computer while it is installing. Be patient.
7. When it ask for a restart to complete the installation, click restart. This can take longer than normal, there are probably thousands of files to overwrite and place in the correct location. Do nothing while this is going on.
8. Once your Mac is awake, repair permissions again, and you should be good to go!
If your Mac seems slightly sluggish or ‘different’, perform a second restart. It can’t hurt and is sometimes efficacious! In fact a second restart can be recommended.
9. Open a few of your most used applications and check that all is OK. In this connection please remember that not all manufacturers of third party applications and plug-ins, add-ons, haxies etc, will have had time to do any necessary rewrites to their software to make them compliant with the latest version of your operating system. Give them a week or two while you regularly check their websites for updates.
N.B. Do not attempt to install two different updates at the same time as each may have different routines and requirements. Follow the above recommendations for each update in turn.
Lastly, Apple's own article on the subject of Software Update may also be useful reading:
http://docs.info.apple.com/article.html?artnum=106695
[b]If you are updating Safari (or just have):[/b]
Input Managers from third parties can do as much harm as good. They use a security loophole to reach right into your applications' code and change that code as the application starts up. If you have installed an OS update and Safari is crashing, the very [i]first[/i] thing to do is clear out your InputManagers folders (both in your own Library and in the top-level /Library), log out and log back in, and try again.
So, disable all third party add-ons before updating Safari, as they may not have been updated yet for the new version. Add them back one by one. If something goes awry, remove it again and check on the software manufacturer's website for news of an update to match your version of Safari.
Most errors reported here after an update are due to an unrepaired or undetected inherent fault in the system, and/or a third party add-on.
Additional tips on software installation here:
http://docs.info.apple.com/article.html?artnum=106692
To reiterate, Input Managers reach right into an application and alter its code. This puts the behavior of the affected application outside the control and responsibility of its developers: a recipe for problems. That's not to say that issues absolutely will ensue as a result of Input Managers, but you, as a user, must decide. If the functionality of a specific Input Manager or set thereof is really important to you, you may well choose to assume the associated risk.
Again, the advice is to remove all Input Managers from the following directories:
/Library/InputManagers
~/Library/InputManagers
especially prior to system updates (they can always be added back one-by-one later).
Solutions for troubleshooting installation, startup, and login issues in Mac OS X v10.5
http://support.apple.com/kb/TS1541?viewlocale=en_US

Do I need to update Bootcamp 3.3 after upgrading from Snow Leopard to Mountain Lion?

Do I need to update Bootcamp 3.3 after upgrading directly from Snow Leopard to Mountain Lion? If so, what is the recommended version for my machine?
Other pros and cons we should consider? Not sure what is considered best practice.
We have a mid-2011 iMac (12,1) running Win7 64bit. Concerned about firmware updates not being compatible with Bootcamp 3.3. Firmware updates forThunderbolt port were part of post-Mountain Lion updater install. Not sure what other firmware/boot changes might have been applied to support the new recovery partition, for example. Will the 3.3 windows control panel still work safely?
Win7 still boots OK, at least for now. Backup is current.
I'd like to get the entire machine current again. Bootcamp 5.0 didn't want to download (appeared to hang writing to my external drive, which is otherwise fine). Bootcamp 4.1 refused to install on Win7 (claimed it wasn't for my machine, so I aborted. Downloaded from apple support page directly).
I've searched the forums for this specific question - I see plenty of info for upgrading Bootcamp 4 to 5, but nothing for 3 to 5.
Thanks much in advance,
-b

Appreciate the quick response.
There are basically 2 schools of thought here:
- If it ain't broke, don't fix it.
- Don't fall off the upgrade cycle (apply patches whether you have an issue or not in order to ward off trouble before it happens).
I don't have a specific issue that I'm chasing on the Win7 side right now. I'm attempting to address having fallen off the upgrade cycle by staying on Snow Leopard too long.
I appreciate that the Win7 side under bootcamp is its own thing (upgrades to Mac OS don't cross over or effect the bootcamp partition) - except where firmware upgrades coming out of Mountain Lion change the hardware interface to Win7. Hence my questions.
-b

Unable to start Hyperion EPM Architect - Process Manager after upgrade

Hi All,
I'm unable to start Hyperion EPM Architect - Process Manager after upgrading from EPMA 11.1.1.3.0 to 11.1.1.3.03. I get the following error in the Event Viewer.
Service cannot be started. Hyperion.DimensionServer.ProcessManager.Interface.ProcessManagerException: Cannot initialize the Session Manager. ---> Hyperion.DataAccessLayerCore.DataAccessLayerException: Database version mismatch: Hyperion.SessionManager schema version is 9.5.0.0.0.10, database schema version is 9.5.0.0.9.1.
at Hyperion.DataAccessLayerCore.DataAccessLayer..ctor(NameValueCollection settings, String tablePrefix, String baseNamespace, String schemaVersion)
at Hyperion.SessionManager.DAO.SessionManagerDataAccessLayer..ctor(NameValueCollection settings)
at Hyperion.DimensionServer.SessionManager.SessionStoreRdbms.Initialize(String rdbmsVendor, String rdbmsConnParams, Int32 rdbmsCommandTimeout)
at Hyperion.DimensionServer.SessionManager.SessionManager.Initialize(String jvmPath, String classPath, String ctgLibPath, String cssConnInfo, String hubHost, String hubPort, Boolean enableNestedGroups, String rdbmsVendor, String rdbmsConnParams, Int32 rdbmsCommandTimeout, Boolean restorePastInstanceSessions, Boolean ...
I've run through all the steps of patching EPMA ran the Oracle_Upgrade 9.5.0.0.0.10 to 9.5.0.0.9.1.sql script per the patch readme. But can't figure out where it's pulling the schema version number from. Any ideas?
Thanks,
Chuck

Hi,
you forgot to update the EPMA database. Last step in patching is:
Now, you must run the database upgrade script before starting the process manager.
Run the single database upgrade script that corresponds to your database vendor.
Oracle_Upgrade 9.5.0.0.0.10 to 9.5.0.0.9.1.sql
SQL_Server_Upgrade 9.5.0.0.0.10 to 9.5.0.0.9.1.sql
DB2_Upgrade 9.5.0.0.0.10 to 9.5.0.0.9.1.sql
The scripts are located in the following directory:
%HYPERION_HOME%\OPatch\EPMA_11_1_1_3_01\files\products\Foundation\BPMA\Server\conf\
hope that helps.

Safari not loading some pages; Software Update stalls - Log Provided

Safari won't load certain pages, times out, and Software Update stalls.
Have reset Safari, emptied cache, etc. but no change. May be more pervasive than just Safari. What to do next?
Console log:
2007-02-20 22:26:35.297 System Preferences[343] * -[NSBundle load]:
Error loading code /Library/InputManagers/MagicMenuEnabler/
MagicMenuEnabler.bundle/Contents/MacOS/MagicMenuEnabler for bundle / Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle, error code 2 (link edit error code 0, error number 0 ()) 2007-02-20 22:26:35.299 System Preferences[343] * -[NSBundle load]:
Error loading code /Library/InputManagers/Menu Extra Enabler/Menu Extra Enabler.bundle/Contents/MacOS/Menu Extra Enabler for bundle / Library/InputManagers/Menu Extra Enabler/Menu Extra Enabler.bundle, error code 2 (link edit error code 0, error number 0 ()) 2007-02-20 22:28:12.317 Software Update[348] * -[NSBundle load]:
Error loading code /Library/InputManagers/MagicMenuEnabler/
MagicMenuEnabler.bundle/Contents/MacOS/MagicMenuEnabler for bundle / Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle, error code 2 (link edit error code 0, error number 0 ()) 2007-02-20 22:28:12.320 Software Update[348] * -[NSBundle load]:
Error loading code /Library/InputManagers/Menu Extra Enabler/Menu Extra Enabler.bundle/Contents/MacOS/Menu Extra Enabler for bundle / Library/InputManagers/Menu Extra Enabler/Menu Extra Enabler.bundle, error code 2 (link edit error code 0, error number 0 ())
MacBook Pro 15" Mac OS X (10.4.8) 2 GB RAM

Hi Terry
Error loading code
/Library/InputManagers/MagicMenuEnabler/
MagicMenuEnabler.bundle/Contents/MacOS/MagicMenuEnable
r for bundle /
Library/InputManagers/MagicMenuEnabler/MagicMenuEnable
r.bundle, error code 2 (link edit error code 0, error
number 0 ()) 2007-02-20 22:26:35.299 System
Preferences[343] * -[NSBundle load]:
Error loading code /Library/InputManagers/Menu Extra
Enabler/Menu Extra Enabler.bundle/Contents/MacOS/Menu
Extra Enabler for bundle / Library/InputManagers/Menu
Extra Enabler/Menu Extra Enabler.bundle, error code 2
(link edit error code 0, error number 0 ())
2007-02-20 22:28:12.317 Software Update[348] *
-[NSBundle load]:
Error loading code
/Library/InputManagers/MagicMenuEnabler/
MagicMenu Enabler is a product developed by the
people who make Stuffit. From the above log it
appears that it might be compromising your system,
and possibly contributing to the problem you are
seeing.
Go to your Main Library>InputManagers folder and
remove the MagicMenuEnabler plug-in (for the time
being move it to your desktop).
Then restart Safari.
Post back
Thanks, Joseph. Tried it last night on my laptop and it didn't help. I still have lots of similar error messages not related to Stuffit. I am getting frustrated. Sometimes Safari is OK, but I have great difficulty logging in to secure sites like my bank and brokerage accounts. Software Update still stalls. Sometimes I have difficulty logging into this site. But, some websites load OK. I can access all of them on my Windows computer in my office.

WIP status (RESA) not updated for process order with co-product

Hi,
We are facing the scenario below, please confirm whether item 2 behaviour is standard SAP.
1. Process order with settlement rule MAT - after WIP calculated, status RESA is updated & FI document it posted.
2. Process order with settlement rule OIT (co-product) - after WIP calculated, status RESA not updated & FI document posted.
Thank you.

Self found answer

Difference in risk analysis results post sp upgrade

Hi Team,
Recently we upgraded our GRC component in dev box to SP level 14. We reactivated the BC sets and ran all sync jobs.
Now the risk analysis results are very different from the non upgraded system.
Do we need to activate BC sets post SP upgrade ? Also how will be the latest rule sets released by SAP imported into the system ?
Thanks in advance.
Regards,
Anil

Hi,
Isn't ANALYZE outdated for R12?
You may still use the Analyze command in 11g Database (R12 is application version), and is not obsolete.
Please refer:
Analyzing Tables, Indexes, and Clusters
Ask Tom &quot;analyze in 11g ,not obsolete?&quot;
How would this resolve the issue?
If the optimizer is not updated with the latest statistics in database, then the COUNT(*) will not be updated and as a result the count will be showing a lower value.
I suggested you to perform an analyze or gather schema statistics in order to eliminate probable cause for the issue.
Thanks &
Best Regards,

Where can i get detail process and command upgrade CRS 10.1 to CRS 10.2?

where can i get detail process and command upgrade CRS 10.1 to CRS 10.2?
I want upgrade CRS/RAC from 10.1.0.4 to 10.2.0.4 (HP-UX)

Pl do not post duplicates - Plese check command upgrade from crs 10.1.0.4 to 10.2.0.4

Update Work Process - Different value in SM51 & TU02...which is correct?

Hi,
i am checking update work process configured in the system.
In SM51, i am getting 36 update work process but when i checked it through transaction
TU02 -> Active parameter, i found the parameter rdisp/wp_no_vb value is 16.
Am surprised to see the different value at different place, how its possible.
which is true, how many update work process is configured in the system?
regards,
Rakesh

Hello Rakesh Ranjan,
We all realized that you already solved the problem but unfortunately you closed this message without saying anything, what had actually happened and how you solved this problem... if you don´t mind share with all community (so that in future other users can solve the same situation with this post!
Best regards,
João Dimas - Portugal

If I upgrade my leopard computer to snow leopard via an old update disc, can I then upgrade to Mountain Lion for the $20 deal?

If I upgrade my leopard computer to snow leopard via an old update disc, can I then upgrade to Mountain Lion for the $20 deal?

Yes, provided your computer meets the system requirements and you have updated Snow Leopard to 10.6.8:
After you install Snow Leopard you will have to download and install the Mac OS X 10.6.8 Update Combo v1.1 to update Snow Leopard to 10.6.8 and give you access to the App Store.
Apple - OS X Mountain Lion - Read the technical specifications.
Macs that can be upgraded to OS X Mountain Lion
iMac (Mid 2007 or newer)
MacBook (Late 2008 Aluminum, or Early 2009 or newer)
MacBook Pro (Mid/Late 2007 or newer)
MacBook Air (Late 2008 or newer)
Mac mini (Early 2009 or newer)
Mac Pro (Early 2008 or newer)
Xserve (Early 2009)
I would also read this:
Make Your Own Mountain/Lion Installer
1. After downloading Mountain/Lion you must first save the Install Mac OS X Mountain/Lion application. After Mountain/Lion downloads DO NOT click on the Install button. Go to your Applications folder and make a copy of the Mountain/Lion installer. Move the copy into your Downloads folder. Now you can click on the Install button. You must do this because the installer deletes itself automatically when it finishes installing.
2. Get a USB flash drive that is at least 8 GBs. Prep this flash drive as follows:
Open Disk Utility in your Utilities folder.
After DU loads select your flash drive (this is the entry with the mfgr.'s ID and size) from the left side list. Click on the Partition tab in the DU main window.
Under the Volume Scheme heading set the number of partitions from the drop down menu to one. Set the format type to Mac OS Extended (Journaled.) Click on the Options button, set the partition scheme to GUID then click on the OK button. Click on the Partition button and wait until the process has completed.
Select the volume you just created (this is the sub-entry under the drive entry) from the left side list. Click on the Erase tab in the DU main window.
Set the format type to Mac OS Extended (Journaled.) Click on the Options button, check the button for Zero Data and click on OK to return to the Erase window.
Click on the Erase button. The format process can take up to an hour depending upon the flash drive size.
3. Locate the saved Mountain/Lion installer in your Downloads folder. CTRL- or RIGHT-click on the installer and select Show Package Contents from the contextual menu. Double-click on the Contents folder to open it. Double-click on the SharedSupport folder. In this folder you will see a disc image named InstallESD.dmg.
4. Plug in your freshly prepared USB flash drive. You are going to clone the content of the InstallESD.dmg disc image to the flash drive as follows:
Double-click on the InstallESD.dmg file to mount it on your Desktop.
Open Disk Utility.
Select the USB flash drive from the left side list.
Click on the Restore tab in the DU main window.
Select the USB flash drive volume from the left side list and drag it to the Destination entry field.
Drag the mounted disc icon from the Desktop into the Source entry field.
Double-check you got it right, then click on the Restore button.
When the clone is completed you have a fully bootable installer that you can use without having to re-download Mountain/Lion.
Note: The term Mountain/Lion used above means Lion or Mountain Lion.
As an alternative to the above you can try using Lion DiskMaker 2.0 that automates the process.

Tetsing post CRM Upgrade

Hi Folks,
We here would soon be starting work on a CRM upgrade from 5.2 to 6.0. The client has some custom code. What should be the testing strategy post upgrade?
Are there any specific tests that need to performed on standard code? Or do we just test the custom code thoroughly? Any suggestion or documentation would be appreciated.
Regards,
Munish

Munish,
We just recently completed a CRM 52 to CRM 60 in our development system and basically my testing strategy was the following:
1. Run through core business process scripts on the system to validate they still work
2. Pay special attention to areas you customized and note any breaks.
3. Compare end to end processes to existing on QA system.
I personally think you still need to do a full test of your processes after the upgrade in the areas that you use. If you don't use a piece of functionality, obviously don't test that.
Now during my unit testing, I paid attention more closely to areas where we deviated further from standard, but still made sure the "standard" areas worked.
The key part is to prevent end user issues before they happen, which can only be accomplished through proper testing.
Take care,
Stephen

PWM duty cycle update stalls

Hello
I want to output a variable pulse width modulated signal via counters. The duty cylce should follow a sine or triangle pattern from 10 to 90 percent.
Problem: When I observe the ctr output with an oscilloscope, I see that the update stalls, i.e. for some time, the output is seamlessly variable as expected, but then, update stalls and jumps to a new duty cycle to continue variable again.
I tried several different approaches,
-for-loop with wait ms- timing and single sample,
-timed loops with single sample and
-pulse train ouptut via DaqMX-Write-Counter-n-Samples.
Albeit to no avail. In any case, I get jumps in the PWM duty cycle instead of smooth transitions.
System is either cDAQ 9174 or PXI with 6602. As system load is 99% idle state, I can't imagine the OS at fault.
Solved!
Go to Solution.

Hello, Frank
After looking through some documentation, I think that I need RT-HW for what I want.
6602 cards have STC-2 without buffer, so updating duty cycle is OS-limited. Even in timed loops there is no guarantee that update will run at the specified rate of 1/140 sec. I'll probably just get an error for untimely execution....
With STC-3 based counters (such as cDAQ9074 or X.series PXI 6361) I can load 127 values into buffer which will be processed smoothly but on renewal of samples (every 127/140 sec), I get stalls again, since the OS seems to consider my request inappropriate. I was surprised to find that USB vs PXI does not change the behaviour, though I'd have expected better latency from PXI.
Attached, please find a VI to get an impression of what I tried out. Pardon for code ugliness.
I still hope that I maybe have missed something simple to get running with what HW I got
Best regards
Michael
Attachments:
Unbenannt 1.vi ‏172 KB

Updating Stalled Process Post ES2 Upgrade

Similar Messages

Maybe you are looking for