Sc version info

Hi,
I created a track which deals with a SC A. Now the same SC should also be transported to a connecting track. so I defined the same software component SC A while creating a track.
When I checked in an activity, it goes thru CMS and after assembly a Sc with build number (say 123 is created) and after approval it goes to the dev system of connecting track and also to prod system of mainline track.
so now in the connecting track, the SC with Build nr 123 is available in DEV tab. and again this has to go through assembly process, which means that a new build, 145 is created. so when I view the system state in the production system and the system in my connecting track, they show a different build nr for SC A. doesnt that mean that my SC in the main track and follow on track is not in sync.
when I have only one system in connecting track, what should i define it as ..i.e which runtime sytem , DEV, CONS, TEST AND PROD. what is the best practice here.
Thank you

Hi Helmut,
Yep, you are correct. This is regarding the track to training systems.
the link was helpful. i didnt understand one point.
1. It was mentioned that while creating follow-on tracks, we should specify "the required SC's". what should I specify here
a) should I specify only SCA, the software component that I developed in the main track
b) should I specify the three base SC's, i.e. sap-jee, jtech services and build tool.
c) should I mention all, i.e. my SCA and also the three base SC's over there.
could you please clarify?
Thank you

Similar Messages

[Developer] How to RELIABLY get Acrobat Reader Version info from registry

(Using Wise Installation system 9.02)
First, we get the path from here:
SOFTWARE\Classes\SOFTWARE\Adobe\Acrobat\Exe
if it is not found, we get it from here:
SOFTWARE\Classes\Applications\AcroRD32.exe\shell\Read\command
and if it is still not found, we get it from here:
SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\AcroRd32.exe
Then we check the version info for the file AcroRd32.exe that is
located in one of those directories and compare it to the version
we are installing; if it is less, we install the version included
in our setup package.
Now, is this the most RELIABLE way to do this?
Should we just search for the file and get it's version info?
What if you have > 1 version of Reader installed?
What if you have Full Acrobat installed?
Is there also a way for Reader installation to NOT change the
PDF file association from Full Acrobat?

If you look at our current process, you'll see that we are checking
for multiple versions. However, there have been times when our version
installed over a later version and we cannot understand why this
happened that is why I'm addressing this here to see if anyone had
any "fool-proof" way to do it.
I know I can also check the PDF association but it may be set to Acrobat
and we do not want to modify that. We just want to check the latest
version of Reader they have installed against the one we have in our
package.

Target setting / version info

Hello,
when releasing a new version of a software I usually update the 'version info' dialog in the target settings. I just realized that these settings are different for debug and release mode... why is it so? One is going to distribute the release version, not the debug version, so why are there two separate entries one has to maintain? Typically, I am running the debug mode, and only at the very end I switch to relase mode. Hence typically I adapt the settings in the debug mode (year, major/minor release number) - so far I had assumed that this is the identical version info as for the release mode, but no...
Wolfgang
Solved!
Go to Solution.

1) The history of this is as follows:
a) From the beginning of CVI, there was always a version number which applied to all binaries that you created. There were no configurations then. Also, there was no such thing as auto-increment. Users would have to explicitly set the version number to whatever they wanted.
b) Some time later, the notion of separate release and debug configurations was introduced. The version info, along with almost all other options, applied to both configurations. There was still no auto-increment.
c) Then, auto-increment was added. When auto-increment is enabled, the simple act of building your project would change the version number. But because the version number was shared accross configurations, and it didn't make sense for debug builds to "interfere" with the release build number, auto-increment was only enforced in release builds -- hence that sentence in the help.
d) The 64-bit configurations then came along. This simply increased the number of configurations from 2 to 4 but had no meaningful impact on this issue.
e) Custom configurations were introduced in CVI 2010. This required most global options to become configuration-specific. We added a note to the readme alerting users to be careful when editing these options, since they were no longer changing all configurations, but just the current configuration. This change also applied to the version field, which could now be different between debug and release builds. At this time, we could have allowed auto-increment to work for debug builds too, since it would no longer interfere with the release version number, but for the sake of not changing existing behavior unless it was absolutely necessary, we decided to continue not supporting auto-increment for debug builds. Users can still change their debug version number to whatever they chose, but it continues not incrementing with each build.
2) This is what I was talking about earlier when I was explaining the purpose of dimming. The values are different, but CVI can only show one, hence it picks one, and dims the value text -- as a visual indicator that it's not the same value for all configurations. Just like in the example of the numeric controls that I gave earlier. This only affects what you see when you first display the dialog. You can still change it, and the change will apply to all configurations.
3) This is probably happening because the name of your program, under the 64-bit configuration, is still MyEarlierProgram. In the Target Settings dialog, cycle through the configuration ring while looking at the application file name. Is it really the same for all configurations? If it's not, then you'd expect %basename (and %filename) to appear differently when you preview the Version Info dialog. %basename is not version-dependent, as you said. It's configuration-dependent.
Luis

How to get rid of webutil version info?

I created a form to test reading and writing files on the client using webutil. (forms 11.1.1.4) which is something I need for my
forms6i -- forms11 conversion.
But it has an issue which is when the form starts it prints out a screen with webutil version info on it. (Webutil Information) .
I see this stuff is on the webutil_canvas. That's interesting but I don't need that in the form. That would confuse the users.
Unfortunately if I open this canvas I get:
"Frm-13008 Cannot find javabean with name oracle.forms.webutil.ole.Olefunctions"
oh oh. That doesn't sound good...
but anyway how do I best get rid of it showing this screen?
I thought I was following instructions correctly for subclassing the object library in my test form. (famous last words.)

Oh never mind I found it.
It does not work to change the webutil_canvas to NOT raise_on_entry. But it does work to put a block before the webutil block.
It seems that if webutil is the first block it has the ability to raise that canvas no matter what but I don't know how it does it.

File version info

I would like to find a way to get the file version info of an exe. I have tried the file info from openG but it does not get the version info. I looked on the MS website and found the .NET function called file version info that is supposed to be under system diagnostics but when I bring up the constuctor node it does not show up . Everything else that is supposed to be in there shows up. I want this info so that I can create a generic about dialog box for my exe. If anyone knows of an easier way to do this I would appreciate any answer.
PS I used the application builder to set the version Info..
Using LV 8.0
Joe.
"NOTHING IS EVER EASY"

Jarrod S. wrote:
Hi Rolf,
Thanks for your
help with the VarFileInfo\Translation resource. I realized this was a
hole in the programs functionality, and I knew a workaround, but I was
never sure how valid the workaround was. Defaulting to the English
language code does sound like a good idea. It definitely works for
LabVIEW.exe. I never bothered implementing this since this was designed
for LabVIEW-built exes, not LabVIEW itself. LabVIEW-built exes do
contain the VarFileInfo\Translation resource. I also built this in
LabVIEW 8, since that was the first version that allowed users to
specify executable versions and other info for their applications. But
it is nice as a general tool!
Hmm, thinking about
it there is possibly one more improvement. If the default english
language does not provide any string resources another possibility
might be to retrieve the current language codes from the user settings
and try with them too. But this sounds quite academical as I can't
imagine an installer manipulating the version resource of an executable
according to the currently set user language. I will have to
investigate a little more what the issue is with files not containing
any translation keys.
As to manipulating the version resource of LabVIEW executables I have
made some code too for this in the past for earlier LabVIEW versions
but found that manipulating the exe part of an executable in any way
after it has been built into an application renders the executable
unusable to run as there needs also to be some modifications at the end
of the file to point to the start of the embedded LLB in the
executable, so that was why I haven't made a tool of this yet. Glad to
see that LabVIEW 8 finally has support for adding a proper version
resource to the executable.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Failed to run the action: Install Software Updates. CI Version Info timed out?

Hi,
I have a task sequence that runs on servers to automatically install the advertised updates in software center. I have one server that is not installing these updates and from the smsts log I see an error about "CI Version times out" Does anyone
know what this means? TIA
<![LOG[One or more updates failed to install, hr=0x87d00314]LOG]!><time="06:37:50.387-120" date="04-25-2015" component="InstallSWUpdate" context="" type="3" thread="31312" file="main.cpp:202">
<![LOG[Process completed with exit code 2278556436]LOG]!><time="06:37:50.387-120" date="04-25-2015" component="TSManager" context="" type="1" thread="26924" file="commandline.cpp:1123">
<![LOG[!--------------------------------------------------------------------------------------------!]LOG]!><time="06:37:50.387-120" date="04-25-2015" component="TSManager" context="" type="1"
thread="26924" file="instruction.cxx:804">
<![LOG[Failed to run the action: Install Software Updates.
CI Version Info timed out. (Error: 87D00314; Source: CCM)]LOG]!><time="06:37:50.434-120" date="04-25-2015" component="TSManager" context="" type="3" thread="26924" file="instruction.cxx:895">
<![LOG[Set authenticator in transport]LOG]!><time="06:37:50.434-120" date="04-25-2015" component="TSManager" context="" type="0" thread="26924" file="libsmsmessaging.cpp:7734">
<![LOG[Set a global environment variable _SMSTSLastActionRetCode=-2016410860]LOG]!><time="06:37:50.636-120" date="04-25-2015" component="TSManager" context="" type="0" thread="26924"
file="executionenv.cxx:668">
<![LOG[Set a global environment variable _SMSTSLastActionSucceeded=false]LOG]!><time="06:37:50.636-120" date="04-25-2015" component="TSManager" context="" type="0" thread="26924" file="executionenv.cxx:668">
<![LOG[Clear local default environment]LOG]!><time="06:37:50.636-120" date="04-25-2015" component="TSManager" context="" type="0" thread="26924" file="executionenv.cxx:807">
<![LOG[The execution engine ignored the failure of the action (Install Software Updates) and continues execution]LOG]!><time="06:37:50.652-120" date="04-25-2015" component="TSManager" context="" type="2"
thread="26924" file="instruction.cxx:962">
<![LOG[Set authenticator in transport]LOG]!><time="06:37:50.652-120" date="04-25-2015" component="TSManager" context="" type="0" thread="26924" file="libsmsmessaging.cpp:7734">

Please have a look at this similar post:
https://social.technet.microsoft.com/Forums/en-US/7ebe1966-1417-4e5e-ba29-1aac6b5b0de1/sccm-2012-deployment-of-updates-failes-with-ci-version-info-timed-out?forum=configmanagersecurity
My Blog: http://www.petervanderwoude.nl/
Follow me on twitter: pvanderwoude

Dynamically load the Version info from maven

Hello,
I am working on a project which is managed by maven.
I want to load the version info marked in project.xml(conf file for maven) from my swing app.
One way is to generate a class holding a static attribute indicating Version using maven.
Anyone has some other suggestions?
Thanks in advance

Hello,
I am working on a project which is managed by maven.
I want to load the version info marked in project.xml(conf file for maven) from my swing app.
One way is to generate a class holding a static attribute indicating Version using maven.
Anyone has some other suggestions?
Thanks in advance

All deployments reporting 'CI Version Info timed out'

Hi guys,
I've had a recent development where all deployment monitoring is reporting 0% success all of a sudden.
Everything was working fine up until a few weeks ago, then I came in one morning and noticed all of my deployments were now reporting varying percentage of errors. Over time the success percent went all the way down to 0% for almost all deployments.
However, the actual deployments themselves are successful. As in the software is installed and logs report success.
Using the 'Application Infrastructure Errors' report, they are all now reporting 'CI Version Info Timed out'.
I've followed so many threads on here suggesting redeployment, updating content, updating memberships of collections etc. I've had no luck at all.
If I look on an example client I see the DCMReporting log has a few errors of 'Failed to resolve version for scope xxxxxxxxx' and the CIDownloader log reports 'Failed to delete Instance Policy xxxxxx'
I haven't made any infrastructure changes to the actual SCCM build in quite a while, though I did restart the server recently.
Any help is greatly appreciated!

Just wanted to leave an update for any future Google'rs.
I may have resolved the issue, I'm just now waiting but after an hour the success rates are climbing back up across the board. After looking through all of the CIxxxxxx.log files and identifying the applications reporting the xxxx - version not found, I
completely removed those apps and re-added them.
This seemed to work so far.
Even though I had previously done this and failed, there was actually multiple apps with this issue. So I had previously done this for 1-2 apps, and the issue still reoccured, which made me incorrectly assume that this wasn't related to the problem. Following
it through I readded another 2 applications and started to see the log files clear and the success rates rise.
Still no call as to what caused it?
For those experiencing this, check your CIAgent.log for the following (taken from the linked post)
CIAgent.log
(The prod version of this app is "12", below you can see the TS was still using version "10"
CIAgentJob({BB81C59E-0D68-4F80-8C26-F3672FDA6993}):
CAgentJob::VersionInfoTimedOut for ModelName
ScopeId_FBAD85CC-8425-4A82-9A2A-A69D6941A909/RequiredApplication_826f927c-b7b4-446b-9767-9e03529677ff, version
10 not available.
CCIInfo::SetError - Setting CI level error to (0x87d00314).
<- this repeated many times
VersionInfo ModelName=ScopeId_FBAD85CC-8425-4A82-9A2A-A69D6941A909/RequiredApplication_826f927c-b7b4-446b-9767-9e03529677ff,
Version=10, IsVersionSpecific=TRUE timed out
I then used the following powershell command to generate a list of Display names and UID's:
Get-CMDeployment | select SoftwareName, ModelName |Out-GridView
and just manually found the matching UID.
I then just manually removed all deployments and then the deployment type. Simply readded the deployment type and redeployed.
Hours later and seems to be on the mend. Hopefully by tomorrow everything will be back to normal.
Note: We did have a UPS failure a few weeks ago that took out power to the ESX cluster. I can't confirm for sure that this was related but it seems to have happened around the same time...

WRT350n firmware and version info

hey guys i noticed that the canadian site shows a different firmware for my router 103.2 and the USA site shows 103.7 is it safe to use the usa firmware as its newer.
also when i look under my router for the version info it just shows the model WRT350N does this mean it a Version 1

if you're not seeing any version # beside the model underneath the device then yes it's version 1

Passing application version info during .jar/.class creation

Is there a 'best' way to supply version info during the application build process so that it is then available at runtime? I use make to build a jar file that then is released. I'd like to be able to provide a release/version number when I build that the user can then access via an 'About' dialog. In 'C', I use preprocessor directives passed via the make command line but I can't see how Java might support this method. Any and all help appreciated...
Thx, Jennette

An Ant script might do stuff like that.

Can I get the version info using the SDK?

Can I get the verion info from the SDK (Web Services SDK or Enterprise SDK)? For instance, for BOE XI R2, I can get some info like this "boexir2", so that I know jar files are for BOE XI R2. If this info can be retrieved, could you please tell me how I should do? Thanks.

Sure, but the odds are that you'll find the regular non-upgrade boxed version for less than the upgrade price, especially as we get nearer the holidays.

Nice Version Info Display

Has anyone seen a component for displaying robust version-control information on a folder item?
The property sheet doesn't contain important details like who modified what when. That information is probably in the database, and could be gathered into a nice view as is common to other version control systems.
Has it been done by anyone? It's a prerequisite for us to use Oracle versioning as anything more than a nicety.

I think Gerhard means info about a element, not a model.
Btw.: This function is helpful for us as well.
take care,
jan masaryk
Gerhard Schneider wrote:
> Well, unfortunately not. The copyright is an "official" function of the
> EPFC, as there is a field and button to select it and to display it for
> publishing.
>
> What I'm looking for is the possibility to display the information of
> fields in the published version, that exist (i.e., Author, Modification
> Date, Version), but that is (currently) not visible after publishing.
> I assume that this is actually possible by modifying some of the XSL
> sheets in some way, but which sheets and what way exactly?

Putting unix utility visible version info into ear, war, jar files?

I would like to be able to use some unix utility (or java itself without a separate program) to display my version information for jar-like artifacts: ear, war, jar.
In other words, when I build one of these things, I'd like to put my SVN version, date, user name, and maybe some other stuff into it in a way that can be read without a custom program. This needs to be done as part of the ant build (without requiring a custom java program).
For example, one approach would be "strings | grep <special-string>" if I could put something, somewhere in the file that had this as 8-bit character encoding.
For jars, making the jar executable and having the main print it out works, but I don't think that's do-able for ears and wars, and it would be desirable to have a consistent approach.
Anyone already doing this?
Ideas?

For example, I don't think you can specify a mainline in the manifest of an ear or war.
They have pretty strictly defined formats, and I don't want to risk violating a standard by tinkering outside the standard.Possible, but you can always run it as java -cp myWar.war my.utility.Version.
There may be another possibility, but I'm unable to find any reference though:
In my early Java days, I used to work on a system where there was a Unix utility (called something like +"ident"+) that was able to extract version and description info stuffed in a .so file (under which "standard" or proprietary format was the info stored, I don't know).
I used to see it work on individual Java .class files too (from memory we had to put a String constant name "VERSION" in the class) and maybe jar files (I'm unsure).
One of my co-workers at that time had described that as a standard tool, but "ident" turns up nothing of that kind on Google... And I've never since encountered any description of the "VERSION" constant naming convention...
I was young and naive, I hope I were not bluffed by some alias in a custom setup... :o(
Edited by: jduprez on Feb 18, 2010 11:30 AM
OK a bit more reserah turned up [that man page|http://man-wiki.net/index.php/1:ident]. Apparently ident is part of RCS (installed along with CVS), and works by grepping the target file for patterns such as "$keyword: text $" (which is RCS/CVS keyword substitution pattern). Now that it mentions it, I remeber that that's what we put into our VERSION constant's value ("$version : ...$", or something of that kind).
So:
1) it's not so standard after all, you have to install the rcs package on the target host (regardless of whether you use RCS for configuration management, which would probably be a bad idea nowadays)
2) you have to put such formatted strings somewhere in your code or configuration files (easy with Ant, if not genuinely through Subversion)
3) To have it work on jar, war, ear, files, you have to make sure that the file is not compressed (otherwise the pattern might not appear in clear). I don't know whether that's easy to configure using Ant's jar, war, ear tasks.
A bit of a hassle compared to stuffing your own utility class and using java -cp...

Photoshop Version Info

We have several sources using different versions of Photoshop from 7 to CS3. Is there a way to tell what version a file has been created in on a Mac? Get info just says Adobe Photoshop (not much help).
thx
paul

Hi Buko
This is the actual problem being reported to me, putting smart objects etc aside......
Re: Colour breakdowns in the Spot channels. It doesnt seems to automatically recognize a PMS colour as a custom colour from a specific colour book, but rather just indicates it as a CMYK breakdown. I checked all the other colour books, and none of them match the breakdown I was getting.
For example, PMS 102 Breakdown should be 0C 0M 95Y 0K, but when opened in CS the breakdown was 2C 5M 96Y 0K
We noticed some shifting in the CMYK colours as well
The solution seems pretty simple... don't open up Photoshop files in previous versions. I guess that's simple enough except it's a bit tough to tell what version it was created in and we have no control over what version a film house etc might use.
So Buko could this be the CMYK adjustments between the latest Photoshop versions in Pantone mixes or color books ?
thx
paul

Incorrect album version/info

When I played a CD for the first time with iTunes, it asked me to select 1 of 4 versions to import the album info. The version titles were all very similar so I wasn't sure which one to choose and just picked one. It ended up being incorrect. The CD I purchased is the Korean version, however the tracks are listed in Japanese. How can I change this to the correct version?
Is there a way to clear iTunes' memory of this CD so when I insert it again I can select the correct information?

In your case this is not needed becuase you have 10.1.0.4 database
Follow the rest of RN instruction and upgrade the oms to 10205

Weird Version Info in WebAccess after 14.0.2

Hi,
I installed "gw14.0.2-120664_full_linux_multi" and I am seeing weird
Version Information in the Info Dialog of WebAcess:
Code:
---------...

You can use:
*http://releases.mozilla.org/pub/mozilla.org/firefox/releases/latest/win32/

Sc version info

Similar Messages

Maybe you are looking for