Track Bx Analyzer version

Hi,
We have BI 7.0 and our users are using Bex Analyzer version 3.x and version 7.0 we want to track which users are using version 3.x.
Is there a program or a way how we track these users. There a zprogram for tarcking sapgui version but is there an equivalent program for tracking the Bex Analyzer version?
Thanks for your help.

Hi ,
you can use the technical content. Both analyzer versions have different Statisitc events. Thats the way you can separate them.
best regards,
kai

Similar Messages

BEx Analyzer version problem

Hi all,
We are having a problem with RRMX and the BEx Analyzer version that it's launching.
We are running BW 3.5, and all our workstations have both BEx Analyzer 3.5 and BEx Analyzer 7.0 installed. SAPGui version is 6.40 SP26, BEx Analyzer 3.5 has SP12 installed.
Naturally, we want RRMX to launch v3.5 but it keeps launching v7.0. Is there an easy way to configure RRMX to launch the legacy version?
Steps I have tried:
1) Transaction RSZVERSION. This only sets the minimun version of the BEx Analyzer, which does not help us.
2) Registry key LAUNCH_VERSION=LEGACY, under HKEY_CURRENT_USER/SAP/BEx/Analyzer. This had no effect.
3) Modifying BExAddin.xml. This one I found out myself, but it's tricky to distribute. The xml-file has a tag called <LaunchLegacyVersion>, when this is set to False, the correct BEx Analyzer version (3.5) is launched from RRMX. As a default, this is set to true.
Now the tricky part is, that BExAddin.xml seems to be a user-specific file which resides under the current users IsolatedStorage folder (%SystemDrive%\Documents And Settings\%UserName%\Local Settings\Application Data\IsolatedStorage). Under the IsolatedStorage folder, there is a 3 folder deep directory structure, and these directories have names that are randomly generated for each user. This means that I can't possibly know what the BExAddin.xml's path is for every user. Making things worse, the whole IsolatedStorage folder doesn't exist, until a user has started RRMX once.
So the question is: is there a place that I could distribute the modified BExAddin.xml so that the settings would be made global for each user, or is there another way to do this?
Best regards,
Juha Kinnunen

Hi Leo,
Yes I tried the personalization but it seems doesn't work, I don't know why.
I set the personalization in the BEx analyzer according to the help documentation step by step but the variable selection screen still pop up when the workbook is opened.
If I executed the query which contained in the workbook seperately there is no variable selection screen pop up.
And because I don't wanna change the variable, so I didn't uncheck the ready to input.
Thanks for your infomation!

HT5361 Best way to track history of version releases for Apple Mail.app?

Best way to track history of version releases for Apple Mail.app?
A great many of the traditional OSX installtion history items are no longer available in 10.8 One can no longer consult the installation history of the "Software Update" preference pane, because that functionality has moved to the Mac App Store utility. The Systems Information Utility does indeed show *some* installation history, but it does NOT include the Mail.app, for some reason. Fianlly, I can't find a web posting where apple at least provides the list of all recent software updates for mail.
Any suggestions?
Thanks!

UPDATE:
I have partially answered my own question. I found that if go to the History window for the selected file, then double-click the "version" (indicated by the label, which is actually displayed in the "comment" field), it opens the file in html. But, there is a "save as" button in this preview window. If I save the file to a temporary location and optionally, give it a different file name (e.g., to indicate the rev #), I can then go to Windows Explorer, double-click the file, which then launches in a browser window and displays the formatted web file. So this will definately suit my purposes from a audit perspective.
However, I still would like to understand how the tags, branches, and pinning works because that might be a better way?
-Kristen

How are you tracking deployed software versions for traceability?

I am curious how others are tracking deployed software versions in automated test environments.
I am working on a medical device tester and we have a somewhat inefficient method for keeping track of all version numbers. I would like to know what tools are available to automate tracking version throughout a project, from build to viewing later. Or, what methods are typical in this type of environment.
Essentially, we need to be able to say at any given moment what software version is running at 3 remote locations on several deployed systems.
For simply automating the process of viewing the version number programmatically, I found this, but we've had issues with it:
http://digital.ni.com/public.nsf/allkb/D45E3A1E694815AD86257173005CFD36
This solution requires a "separate" installer to get the .NET framework onto the target PC. Also, it doesn't work (to my knowledge) with the Help>>About window.
Comments?
Dan Richards
Certified LabVIEW Developer

Dennis,
Thanks for replying. We are using SVN. The exact ECO process for this project is under construction as it is a relatively new project and deployments will be at our customer's site. We use JIRA for tracking specific change requests.
Here's an example of our basic process:
- Software changes made (according to JIRA tasks) and source code checked in
- Builds released per schedule with version numbers (from JIRA projects) hard-coded into the application
- Builds deployed at different locations & times
Here's what I'd like to see to improve things:
- Builds released with version numbers generated from one of the following:
   1. Loaded from JIRA release numbers - maybe auto-generated for reference by LabVIEW when building the application
   2. Part of a custom build launcher
         >> This would be a custom interface that runs functions like those in Application Builder palette while also sending version info
         >> Perhaps it could prompt the user for version info or read from something auto-generated.
- Builds should automatically make version numbers visible within the application (for example, LabVIEW has the Help>>About window)
- Build numbers should be programmatically/dynamically accessible without having to install an additional .NET framework that isn't listed in 'Additional Installers'
Curious if there are any tools that support these kinds of things. I am aware of Deploy by Wirebird Labs and Proligent by Averna, although I am lacking in knowledge about specific features.
Regards,
Dan
Dan Richards
Certified LabVIEW Developer

Identify Bex Analyzer version

Hello experts,
If someone is using Bex Analyzer to execute a query, how do you know which version the Bex Analyzer is?
Some users use version 7.00 and others use version 3.x. We want to track those who are using Bex Analyzer 3.x.
Please help,
Chuong

hi ,
can you look at this .....
https://www.sdn.sap.com/irj/sdn/advancedsearch?cat=sdn_all&query=bexAnalyzertoexecutea+query&adv=false&sortby=cm_rnd_rankvalue
regards,
venkat.

Trial version problem when using more than 1 track - does trial version same as full one?

I am thinking of upgrading to Premiere Elements 9 as I have upgraded my laptop. But the trial version Premiere Elements 9 doesn't even perform as well (with the same media) as Elements 4.0 did on my old laptop.
My new laptop is an HP Pavilion with Intel(R) Core i7 Q720 @ 1.6GHz (I was a bit wary of the low GHz but HP explained that that was still better than a higher GHz figure for an i5). I am editing both MP4 and avi files at 720 x 480.
The problem is that as soon as I start to use more than a couple of video tracks, playback slows right up, making editing difficult. Other software packages I have trialled on the new laptop (such as Sony Vegas) don't slow up at all, but I'd rather not buy them as I am very familiar with Premiere Elements now.
Is this a problem with the trial version which woudl be solved if I bought the full version, or will it be the same?
Thanks very much for any help

The AVI format is but a wrapper. Almost anything can be inside that wrapper. This ARTICLE will give you more background, and will also tell you how to determine what is inside the wrapper.
Especially with a laptop, I strongly recommend tuning the computer for an editing session. This ARTICLE will give you some tips. Note: there are a couple of links, just for Win7. Also, there are some good tune-up tips in the forum FAQ section, to the right of the main forum page. Of special note: the active anti-virus, pop-up blockers and spy sweepers are known to cause all sorts of problems, when trying to edit video.
One major consideration with a laptop is the I/O sub-system - the HDD's. Most laptops only have one internal HDD, and that is anything but ideal. With eSATA external HDD's, one can get very nearly the same performance, as with multiple internal HDD's. This ARTICLE will give you tips on using external HDD's with video editing. Though I have 3x internal SATA HDD's in my laptop, I still rely on FireWire 800 (IEEE-1394b) externals, and they work well. Using eSATA would be even better. For more info on the I/O sub-system, see this ARTICLE.
Good luck,
Hunt

What does DIAdem do to keep track of multiple versions of itself?

I am using an automation reference to open up DIAdem. I have 8.1 and 9.0 installed. If I run DIAdem 8.1 and close it, then the reference gives me 8.1. If then I run DIAdem 9.0, the reference gives me 9.0. So the computer must be keeping track of the program that was run most recently. How does it do this?

I don't have two versions on this computer so I can't play with it to find the exact key, it's probably going to be under HKEY_CLASSES_ROOT\TypeLib\ somewhere, but it'll be under the Class ID rather than the name.
Regards,
Ryan K.

How does DIAdem keep track of which version is active when multiple versions are installed?

I need a way to find out which version of DIAdem is active, without creating an automation reference. How does DIAdem keep track of this? I don't think it's through the registry as far as I can tell. Thanks.

Hi,
I'm not quite sure what you mean by "version of DIAdem is active". If you are trying to reference DIAdem from an external program, you will need to use an automation reference. Besides this case, I am not sure what you are referring to.
Perhaps a short description of your application or intended use will help me point you in the right direction.
Allen P.
National Instruments

Camera for tracking with student version?

Hi all,
Im just researching some of the advanced features of LabView. I'm very new (programming 3 weeks). I have done most of the tutorials and built a few functional VI's to practice my basic understanding of tools. my question is just how to connect the camera for tracking VI into my USB camera?
Any links that have helpful information is apperciated.
I am hoping that the Student Version of LabView doesnt restrict me from some of these cool features.

Hello,
In order to acquire images from a USB camera, you will need to use the IMAQdx driver which is part of Vision Acquisition Software. This driver requires a license in order to be used and has a 30 day trial if you do not activate it. If you get ahold of a license, the thing to note is that your USB camera must be DirectShow compliant in order to work. There are a number of shipping examples (Help»Find Examples) that acquire from IMAQdx cameras once you install Vision Acquisition Software.
-Zach
Certified LabVIEW Developer

[Java and all else] Requirements tracking, testing, and versioning

Hello,
as a semi-experimental subject, I am considering managing requirements and test documents in the same version control system as the code.
For some reasons, this versioning policy doesn't seem mainstream, so I'd like to have your opinion on that.
+N.B.: the prefix "java and all else" refers to the fact that I'm using this area to post a message that is related not only to Java but also to other topics (people, processes, tools,...) that help program in Java - so this post is not really off-topic either. For the record, I filed a suggestion to open a dedicated forums to discuss topics like that, although it hasn't received enthusiastic support so far :o(...+
Here is how I had imagined to proceed:
- requirements document gets edited and stored as text in the VCS
- test plan (basically a matrix of which tests cover which requirements) goes into the VCS as well, text or binary
- test instructions (detailed steps, actions, expected results) are stored as text in the VCS
- test results - I do'nt know yet, but I planned to store them as text (lists of testId=result) in the VCS (I'm not sure indeed, that those would go into the VCS)
The advantage of versioning those as text is that all VCS clients support easy-as-a-click history browsing and diff capabilities.
Diffs and logs are useful to trace when and why a requirement has appeared, evolved, obsolated,... Especially in long-lived systems whose maintenance crew rarely embeds "historical" pioneers who developed the original systems.
My questions:
1) Is it good practice to version such docs in the same repository as the code?
I've never seen this done.
- In half of the shops I've been these docs are not really versioned (the PM considered it enough that the latest applicable version of the docs was available)
- The other half has used versioning systems ranging from ad-hoc (shared folder acting as repository of all versions) to "document management systems". I found such tools to be developer-unfriendly (poor diff capability, poor text searching), and developers to be office-document-reluctant (mostly because of the shortcomings of the doc format and doc management systems).
- The third half <wink to aficionados of French cinema> used dedicated softwares (Test Director, RQM,...) to manage requiremetns, test plans, test cases, test results,... The drawback is that the developers were hardly involved in using such tools, and even when they were, were not trained to use the administrative and metadata capabilities (who modified the test steps, when and why?).
On the contrary, developers would easily and gladly browse histiry, check diffs, etc... on text documents versioned using their daily-used source control system.
2) Are there "standard", preferrably text-based, formats, for the documents listed above?
Each and every organization I've seen had its own format, but most items have equivalents in all organizations, even if disguised under different terminologies. I have no formal education or training in quality assurance, but I guess some ISO or CMM norms define those recurring items, and I expect some abstract XML format might exist
3) Are there tools already that cover edition and exploitation of such formats, or why not, of the versioning of such formats (naive example, graphing the pass rate of tests over time)?
A pet project of mine is to develop and open-source some Swing UI to do this, but existing tools would save me the trouble.
I'm looking forward to reading about your own experience.
Best regards,
Jerome.
Edited by: jduprez on Jun 4, 2010 10:33 PM
Fixed link.

I don't have data on comparative bug rates because we did not do studies focused on that. This stuff was mostly driven by convenience #) considerations.
Subjectively, yes it seemed to have lower bug rate compared to maintaining documents in, say, pdf format (like our doc writers did with User/Dev guides). BTW doc writers are another kind of guys who dislike plain text.
As for using test results history the way you describe - agree, that makes some sense. Now that you mention it I recall using it myself that way, in one of the projects where testers managed to establish really convenient way to assess test execution history. After I figured how easy it was, I began using it. Quite helpful indeed.
Regarding "tool or format that mapped tests to specific requirements" in your original post - did you consider Polarion? IIRC it supports mapping requirements to test descriptions. Telelogic DOORS are maybe also capable of that but I am not completely certain.
#) convenience -- BTW we maintained test descriptions not in plain text but in simple HTML (you know few tags one can use in javadocs). With limited line length, it is almost as VCS friendly as plain text, even with tables:
<!DOCTYPE "stuff to make HTML validator happy">
<html><title>test description</title>
<body>
<table>
<tr>
 <td>test id</td>
 <td>synchronized.10988343</td>
</tr>
<tr>
 <td>instructions</td>
 <td>
 <ul>
 <li>sacrifice a goat
 <ul><li>under the full moon</li></ul>
 </li>
 <li>twirl counterclockwise
 <ul><li>until you barf</li></ul>
 </li>
 </td>
</tr>
<tr>
 <td>pass criteria</td>
 <td>
 <ul>
 <li>pass if method is synchronized</li>
 <li>fail otherwise</li>
 </ul>
 </td>
</tr>
<tr>
 <td>comments</td>
 <td>
 <a href="http://forums.sun.com/thread.jspa?messageID=10988343#10988343">
 click here for details</a>
 </td>
</tr>
</table>
</body>
</html>
{code}
We were also using [HTML validator|http://validator.w3.org/|tool] tool to automatically catch simple syntax mistakes like missing tags.

Tracking down the version number

I have a C/C++ program which is a Firefox plugin. I'm trying to find the version number resource.
In my plist I have: Bundle versions string, short set to 5.09b and bundle version to 1.0
In my .rsrc file (yes, I'm still using rsrc files, it's not my fault.) my vers resource has a short string of 4.70
When I compile, the version on the .app file is 5.09b
When I run the program, I do:
CFBundleRef myAppsBundle = CFBundleGetMainBundle();
bundleVersion = (CFStringRef) CFBundleGetValueForInfoDictionaryKey(myAppsBundle, CFSTR("CFBundleShortVersionString"));
CFStringGetCString(bundleVersion, verString, sizeof(verString), kCFStringEncodingMacRoman);
printf("bundleversion is %s
", verString);
and it gives me 3.5.6. previously, it was giving me 3.5.5.
I've done a bunch of searches through my code, and can't find "3.5.5" anywhere. And the code above works in other projects.

Yes I have.
However, someone else just pointed out that 3.5.5 and 3.5.6 are the most recent versions of FIREFOX! so, I'm getting the info from firefox's bundle, not my own.
How to get access to my own bundle is probably a topic for another question...

Can someone tell me how t delete all the automation of a track in version 9

Dear god in heaven.. can someome please tell me how I can simply "Delete all automation of current track" like in version 8??

Track/track automation/delete all automation on selected track.

Analyzer HTML version

how do i login and load a report via URL all in one call? anybody with this experience please reply thanks Venu Thamodharan, J2EE lead Bank of America example link like this. <a target=_blank class=ftalternatingbarlinklarge href="http://B000F1FB6A4E2:7001/Analyzer7_Server/servlet/HTMLViewer?SID=w1IWRBX4pZIgxYjP29X3J05A&ACTION=FileBrowser&EVENT=SELECT&REPORT=%2FUsers%2FAdministrator%2FReports%2FEmeaTestVenu">http://B000F1FB6A4E2:7001/Anal...eports%2FEmeaTestVenu</a> 

Hi, this can't be done using only one URL address. This must be done using multiple URL addresses, because session ID must be provided. Please look at the following solution: The bottom solution is for Analyzer version 6. Change URL addresses to your Analyzer version. Also change useid and password according to your environment. ====== 1> ====== Add parameter "&portal=1" to end of login string....this tells HTMLViewer to return the session id to client. <a target=_blank class=ftalternatingbarlinklarge href="http://hostname/Analyzer6_Server/servlet/HTMLViewer?ACTION=login&userid=Administrator&password=password&portal=1">http://hostname/Analyzer6_Serv...ord=password&portal=1</a> The client machine gets back following result: 1 1670151848 The number 1670151848 is your session id for this login session and should be used in all following requests by specifying &SID=. ====== 2> ====== Load your report in session ID# 1670151848 <a target=_blank class=ftalternatingbarlinklarge href="http://hostname/Analyzer6_Server/servlet/HTMLViewer?SID=1611792047&ACTION=LoadReport&GROUP=TestHTML&NAME=Sample1">http://hostname/Analyzer6_Serv...TestHTML&NAME=Sample1</a> Hope this helps, Grofaty

CE 7.1 Ehp1 SP5 on Oracle 10.2.0.4 Performance - XSS track import of SCAs

Hi,
I'm currently building a new track on my newly built CE server which has the NWDI capability configured. I've had a few problems importing the SCA files into the track. I've been getting DTR internal server errors. Looking through the logs I couldn't see a specific reason as per OSS 774339 and the subsequent notes this refers to. After restarting the CE server I've imported the SCA files individually and this has at least enabled me to get the SCA files imported without error.
The time taken to import is very long - the ESS SCA file (290 MB) took 3.5 hours alone.
I've read OSS 1361525 which is related to DTR performance with Oracle but the Patch provided is for 7.01 / 7.02 releases of CE.
I have already patched my CE 7.1 Ehp1 SP5 server with the available patches for DICMS05, DICLIENTS05 & DICBS05* - there is none current available for download for the DIDTR05* CE 7.1 Ehp1 release.
Can anyone suggest what could be done to reduce the import runtimes ?.
I'm regularly updating the Oracle Statistics as per OSS 1229080 and the Oracle params have been set as per OSS 830576.
Regards,
Brian.

Hi Ervin,
1. The NWDI Server is a distributed configuration - the DB instance is on it's own Solaris 10 zone and the central services & instance are on another Solaris zone. Both zones have plenty CPU/Memory resources and the load values on both are low. The systems are not overloaded.
2. THis is a new build and I'm setting up the first track to enable the customer to start a XSS development project. The first 10 or so SCs imported without error into the track. ESS, MSS & PCUI_GP SCA files are the ones remaining and are failing to import.
3. Our OS is Solaris 10 on Sun Sparc - so no windows type anti-virus software to contend with.
4. I've run the statistics a few times over the last day or so :-
brconnect -u / -c -o summary -f stats -o SAPSR3DB -t all -p 8 -f nocasc
5. Trace levels are default.
6. The logs & traces have no OutOfMemory errors as per OSS 1001502. The error received is :-
20100908171424 Info   :Starting Step CBS-make at 2010-09-08 17:14:24.0632 +1:00
20100908171425 Info   :wait until CBS queue of buildspace S01_Sandbox_D is completely processed, before starting the import
20100908171425 Info   :CBS queue of buildspace S01_Sandbox_D is completely processed. Starting the import now.
20100908181425 Fatal :CBS throws exception during activation:
20100908181425 Fatal :caused by Exception:com.sap.tc.cbs.client.error.CommunicationException: Read timed out (Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out):Read timed out (Service call exception; nested exception is:
     java.net.SocketTimeoutException: Read timed out)
The interesting thing here is that the error is thrown exactly one hour after the CBS-make operation starts.
7. We've got Oracle DB.
Hopefully you'll be able to suggest how best I can resolve the error and continue.
Also - from the logs there was further error activity for this same import operation 3 hours later after I'd gone home :-
#2.#2010 09 08 21:34:50:064#+0100#Info#/Applications/CBS/Service#
#BC-CTS-CBS#tc.CBS.Service#0021286D058200680000000E000004DB#14060650000000783##com.sap.tc.cbs.server.rt.rq.RequestOrc####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[CBS Request Orc,5,SystemThreadGroup]#Plain##
Request arranged for processing for BuildSpace S01_Sandbox_D. [bsID:3, rID:62, node:14060650]#
#2.#2010 09 08 21:34:50:086#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D058200690000006F000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
Build number assigned: 67#
#2.#2010 09 08 21:34:50:088#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000070000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
Change request state from QUEUED to PROCESSING#
#2.#2010 09 08 21:34:50:095#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000071000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
#2.#2010 09 08 21:34:50:096#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000072000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
REQUEST PROCESSING started at 2010-09-08 20:34:50.095 GMT#
#2.#2010 09 08 21:34:50:098#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000073000004DB#14060650000000783##com.sap.tc.cbs.server.proc.RequestHandler####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    ACTIVATION request in Build Space "S01_Sandbox_D" at Node ID: 14,060,650
        [id: 62; parentID: 0; type: 4]
        [options: IGNORE BROKEN DC, FORCE ACTIVATE PREDECESSORS, FORCE INTEGRATED, IGNORE COMPONENT INTERSECTION]#
#2.#2010 09 08 21:34:50:149#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000074000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
#2.#2010 09 08 21:34:50:150#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000075000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    Waiting for access: 54 ms#
#2.#2010 09 08 21:34:50:151#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000076000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
#2.#2010 09 08 21:34:50:151#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000077000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
    ===== Pre-Processing ===== started at 2010-09-08 20:34:50.150 GMT#
#2.#2010 09 08 21:34:50:152#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000078000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        List of requested for activation activities:#
#2.#2010 09 08 21:34:50:184#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000079000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            ''sap.com_SAPPCUI_GP_1'' compartment#
#2.#2010 09 08 21:34:50:184#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007A000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                CMS_sap.com_SAPPCUI_GP_590_aabfda99de4511d9b84800300530c04f#
#2.#2010 09 08 21:34:50:185#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007B000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                    [ISN 2][created by MAIN at 2010-09-08 17:14:24.0][OID e4fdda79781d11dec2470030057116fe]#
#2.#2010 09 08 21:34:50:185#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007C000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            There is 1 activity in compartment sap.com_SAPPCUI_GP_1#
#2.#2010 09 08 21:34:50:186#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007D000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            1 activity will be processed by this request#
#2.#2010 09 08 21:34:50:647#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007E000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
#2.#2010 09 08 21:34:50:648#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D058200690000007F000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        Analyze dependencies to predecessor activities... started at 2010-09-08 20:34:50.647 GMT#
#2.#2010 09 08 21:34:50:648#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000080000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            Analyzing predecessors in compartment "sap.com_SAPPCUI_GP_1"#
#2.#2010 09 08 21:34:50:669#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000081000004DB#14060650000000783##com.sap.tc.cbs.server.proc.impl.ActivationPreProcessor####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
                No dependencies to predecessor activities found.#
#2.#2010 09 08 21:34:50:669#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000082000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        Analyze dependencies to predecessor activities... finished at 2010-09-08 20:34:50.669 GMT and took 22 ms#
#2.#2010 09 08 21:34:50:670#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000083000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
#2.#2010 09 08 21:34:50:670#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000084000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        Analyze versions... started at 2010-09-08 20:34:50.670 GMT#
#2.#2010 09 08 21:34:50:712#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000085000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            ===== Pre-Processing ===== finished at 2010-09-08 20:34:50.711 GMT and took 561 ms#
#2.#2010 09 08 21:34:50:712#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000086000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            Change request state from PROCESSING to FAILED#
#2.#2010 09 08 21:34:50:713#+0100#Error#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000087000004DB#14060650000000783##com.sap.tc.cbs.server.proc.RequestHandler####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            Error! The following problem(s) occurred during request processing:#
#2.#2010 09 08 21:34:50:713#+0100#Error#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D0582006900000089000004DB#14060650000000783##com.sap.tc.cbs.server.proc.RequestHandler####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
            Error! The following error occurred during request processing:Server error [500 Internal Server Error]#
#2.#2010 09 08 21:34:50:714#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D058200690000008B000004DB#14060650000000783##com.sap.tc.cbs.RequestPerformanceMeter####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
        REQUEST PROCESSING finished at 2010-09-08 20:34:50.714 GMT and took 619 ms#
#2.#2010 09 08 21:34:50:728#+0100#Info#/Applications/CBSRequestLog/RequestProcessing/id67#
#BC-CTS-CBS#tc.CBS.Service#0021286D058200690000008C000004DB#14060650000000783##com.sap.tc.cbs.server.dao.impl.Request####97674940BB5111DFA9180021286D0582#97674940bb5111dfa9180021286d0582#97674940bb5111dfa9180021286d0582#0#Thread[SystemThreadGroup - 70,5,SystemThreadGroup]#Plain##
Regards,
Brian.

All DCs of ESS Mentioned as Dirty DCs in the track

Hi,
We are using a Track in the ESS for the Changes.
All were working fine , we were able to check in code and activate also.
Some changes done in the Track and now i saw that all the DCs in the track are in the Broken state.
In NWDS , we are getting a new configuration messdage.
If we are using the new configuration, we are getting lots of error in the DC.
The below is the error trace in the CBS:
Analyze effect of applied changes to buildspace state... started at 2009-04-21 11:57:50.487 GMT
 INVALID DEPENDENCIES: The following dependencies of the DCs in this request are being marked as invalid as they refer to non-existent public parts.
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/bi/bp/webDynpro' DC, does not exist [public-part: webDynpro] AS Build Plugin Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.aii.proxy.framework' DC, does not exist [public-part: default] AS Build-Time Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.aii.util.misc' DC, does not exist [public-part: default] AS Build-Time Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/cmi' DC, does not exist [public-part: default] AS Build-Time Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/ddic/ddicruntime' DC, does not exist [public-part: default] AS Build-Time Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/ddic/metamodel/content' DC, does not exist [public-part: default] AS Build-Time Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/wdp/metamodel/content' DC, does not exist [public-part: default] AS Build-Time Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.exception' DC, does not exist [public-part: default] AS Build-Time Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/com.sap.mw.jco' DC, does not exist [public-part: default] AS Build-Time Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/logging' DC, does not exist [public-part: default] AS Build-Time Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 'sap.com/BIApp' DC of 'sap.com_SAP_ESS_1' compartment USES 'sap.com/tc/wd/webdynpro' DC, does not exist [public-part: default] AS Build-Time Dependency
 [validity: USED COMPONENT OR PUBLIC PART IS UNKNOWN OR UNDEFINED]: Invalidated
 Skip check for build time dependency cycles. DC metadata is not changed.
Thanks,
Anumit

Thanks Pascal,
Now , i am able to reimport the mentioned DCs. But when i am activating any activity then getting the below error log:
Build number assigned: 11970
Change request state from QUEUED to PROCESSING
REQUEST PROCESSING started at 2009-04-22 08:31:05.378 GMT
 ACTIVATION request in Build Space "EPD_XSSTRACK_D" at Node ID: 15,357,950
 [id: 10,985; parentID: 0; type: 4]
 [options: NO OPTIONS]
 Waiting for access: 58 ms
 ===== Pre-Processing ===== started at 2009-04-22 08:31:05.437 GMT
 List of requested for activation activities:
 'sap.com_SAP_ESS_1' compartment
 medicalrem_remove_info_from _test
 [ISN 53][created by J2EE_ADMIN at 2009-04-14 14:33:18.0][OID 95c9ff2928d211de878900144fa0ee66]
 There is 1 activity in compartment sap.com_SAP_ESS_1
 1 activity will be processed by this request
 Analyze dependencies to predecessor activities... started at 2009-04-22 08:31:05.667 GMT
 Analyzing predecessors in compartment "sap.com_SAP_ESS_1"
 No dependencies to predecessor activities found.
 Analyze dependencies to predecessor activities... finished at 2009-04-22 08:31:05.801 GMT and took 134 ms
 Analyze versions... started at 2009-04-22 08:31:05.802 GMT
 List Active Versions Report: "HTTP/1.1 207 Multi-Status" finished at 2009-04-22 08:31:06.454 GMT and took 527 ms
 Synchronize metadata for [sap.com/medirem] started at 2009-04-22 08:31:06.510 GMT
 Verification of DL [ws/XSSTRACK/sap.com_SAP_ESS/dev/active/] finished at 2009-04-22 08:31:06.623 GMT and took 39 ms
 Verification of cache (level 2: Comparison of attributes) finished at 2009-04-22 08:31:06.696 GMT and took 72 ms
 Synchronize metadata for [sap.com/medirem] finished at 2009-04-22 08:31:06.702 GMT and took 192 ms
 < CHANGE > 'sap.com/medirem' DC
 Analyze versions... finished at 2009-04-22 08:31:06.704 GMT and took 902 ms
 Analyze activities... started at 2009-04-22 08:31:06.705 GMT
 Loading component definitions
 1 component to be build in compartment "sap.com_SAP_ESS_1"
 Analyze activities... finished at 2009-04-22 08:31:06.793 GMT and took 88 ms
 Calculate all combinations of components and variants to be built...
 Analyze request DC BV... started at 2009-04-22 08:31:06.824 GMT
 'sap.com/medirem' variant 'default'
 Analyze request DC BV... finished at 2009-04-22 08:31:07.510 GMT and took 686 ms
 Prepare build environment in the file system... started at 2009-04-22 08:31:07.511 GMT
 Synchronize development configuration... started at 2009-04-22 08:31:07.512 GMT
 Synchronize development configuration... finished at 2009-04-22 08:31:07.517 GMT and took 5 ms
 Synchronize sources for [sap.com/medirem] started at 2009-04-22 08:31:07.563 GMT
 Verification of DL [ws/XSSTRACK/sap.com_SAP_ESS/dev/active/] finished at 2009-04-22 08:31:13.251 GMT and took 47 ms
 Verification of cache (level 2: Comparison of attributes) finished at 2009-04-22 08:31:14.615 GMT and took 1 s 363 ms
 Synchronize sources for [sap.com/medirem] finished at 2009-04-22 08:31:15.273 GMT and took 7 s 710 ms
 Synchronize used libraries... started at 2009-04-22 08:31:15.584 GMT
 DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.
 Used DC 'sap.com/tc/cmi' HAS NO PUBLIC PART 'default'.
 [DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 211 variant 'default'][SCID=76][last successful build: 11532]
 DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.
 Used DC 'sap.com/tc/ddic/ddicruntime' HAS NO PUBLIC PART 'default'.
 [DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 217 variant 'default'][SCID=76][last successful build: 11532]
 DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.
 Used DC 'sap.com/tc/ddic/metamodel/content' HAS NO PUBLIC PART 'default'.
 [DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 218 variant 'default'][SCID=76][last successful build: 11532]
 DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.
 Used DC 'sap.com/tc/wd/webdynpro' HAS NO PUBLIC PART 'default'.
 [DC '778' variant 'default'][SCID=75] using [PP 'default' of DC 85 variant 'default'][SCID=72][last successful build: 11532]
 DC 'sap.com/medirem' in SC 'sap.com_SAP_ESS_1' cannot be built. ACTIVATION will fail.
 Used DC 'sap.com/tc/logging' HAS NO PUBLIC PART 'default'.
 Synchronize used libraries... finished at 2009-04-22 08:31:18.845 GMT and took 3 s 261 ms
 ===== Pre-Processing ===== finished at 2009-04-22 08:31:18.878 GMT and took 13 s 441 ms
 Change request state from PROCESSING to FAILED
Thanks,
Anumit

Track Bx Analyzer version

Similar Messages

Maybe you are looking for