Wasn't getting any responses on other thread - an older thread, "assumed answered" - perhaps no one is paying attention to it. So, copied my last entry and started a new thread, here.
We have our 14.2 system running in Sandbox (SB) environment, now. Ran into the "Writing XML File" issue, then recalled a thread which addressed this topic. I followed the advice there - removed/reinstalled the interface, twice now - once to C: as described in your Tuesday Tip, and once to My Programs under C:\users\[myaccountname]\.
In both cases, I have made some progress (export of project no longer stalls at "Writing XML Files"). Many of my projects now open successfully.
However, I have some projects that stall at "Opening XML files in MSP." Also, where it works, it is not 14 times faster than the legacy interface. My initial testing is showing that it is actually slower.
Times are in mm:ss.
On my machine, running Windows 7 64-bit and MSP2010 32-bit.
Haven't identified a common thread yet, as to what causes a project to open vs. stall. It is consistent though - projects which open, always open; those that stall, always stall.
I think I may have voiced my opinion either on one of your posts or someone else;s, but yes, in my testing with 14.2 the new driver, it is WAY Slower. I have an open case with CA on the new driver. I had so many issues that it is vritually unusable. I really hate the change that the save/loading shows as a tiny tray message at the bottom and does not display the progress upon saving. The legacy driver still does that. If you happen to touch the project while it is saving (maybe one does not notice that it is saving in its teeny message at the bottom), the project will hang. You have to kill MSP-- that is a huge miss in design in my opinion.
I have seen my stall on occasion with the new driver, but it was because I had 2010 and 2013 installed on the same machine. Have you tried doing a full uninstall and installing it choosing the legacy driver and see if that helps? If it opens ok, then it may be the driver issue.. like I Said, I stopped with the new driver. CA has a laundry list of things to investigate on my case
Yes - if I uninstalled and loaded legacy version, it works fine, no issues. I have only one instance of MSP installed, 2010.
Key users have been looking forward to the "14x faster" interface, and certain improvement initiatives we have are dependent on having a faster interface. OWB, though it does interest a few, is not, and may never be, a serious option for us, yet.
I'm also seeing the following:
Yes the locking is one I reported as well. I was not able to get mine to stop. Again, with the legacy driver, I don't have that issue.
We do not use a lot of child projects, mostly just programs
My recent pages icon in Clarity works fine.
I agree about the speed of opening and saving project. On my case, I asked for metrics. We have two very huge defects that we requested to be put in patch 5 as I was told they were fixed in 14.2, but then they were not. That was the main reason for upgrading was the fix of two MSP defects. It would not impact anyone, unless they use the TSV in MSP for forecasting. I can't do much more MSP testing until patch 5, as those are show stoppers. 14.2 as a whole, I have done some regression testing, and so far nothing major (outside of our own causes), but it is pretty early.
Hi Dale - Checking to see if you were able to find a resolution for your issue? Thanks! Chris
The pre-14 drivers prep the project data such as writing up the ETC segments to be accepted by MS Project. With the new driver the raw data is sent to MS Project in an XML format, it is then processed by MS Project including creating the segments. In some situations the XML files have been found to be taking longer than expected to be opened up in MSP. We are collecting more statistics about these types of situations.
Did you see any XML file actually being created while the project is stalling? You can also check the mspxml_timing.log under bin > logs folder to see if any timing information is capture. Schedlogs and debug log (turn on debug for com.niku.schedulers) will also help gauge what data is taking long to be transferred over to MSP.
Hi Connie, nice to hear from you!
Made some progress working with Support out of Islandia, last week. It’s not stalling any longer. However, still having the following issues:
- Performance: About the same as 13.1, non-xml (not 14 times faster as expected from EOS demos)
o If project is closed before saving, interface unlocks project in CA PPM as expected
o If project is saved before closing, interface fails to unlock project in CA PPM
- Have an example of parent/child projects where upon saving parent
o I’m asked 3 times if I want to save child
o Ultimately ends in ‘save failed’
- Mspxml-general.log contains numerous “assertion fails” messages:
- In Mspxml_http.log, numerous GetField errors:
- Mspxml_timing.log – example content
As this opening time is similar to our 13.1 experience, we are expecting a time closer to 5 seconds in order to be “14 times faster.”
- Windows 7, 64-bit
- MSP 2010, 32-bit, with SP2 installed
- NetFrame 4.5 installed x64
- MS Visual Studio 2010 Tools for Office Runtime x64
- MSP xml interface, x86
I have no Java installed.
- I did have Java 7 and 8 installed
- Removed 8, performed all MSP interface uninstall steps, reinstalled MSP interface – no difference
- Removed 7, performed all MSP interface uninstall steps, reinstalled MSP interface – no difference
- The Wiki page on this subject is not clear – stating that “this release uses Java 7” but then only lists XOG and Service Connect as the components that use Java 7 and OWB and MS SharePoint Connect for JRE.
If I do need Java 7/JRE1.7 installed for MSP Interface to work properly, then I’d say the interface wasn’t recognizing the installation when it was there, as taking it out has made ZERO difference.
Will ask app manager to turn on Schedlogs and debug log.
Dale C. Stockman
Technical Specialist-Project Systems
Department Group: Engineering Quality
Department: Braking Engineering
Active & Passive Safety Technology
Business Unit: Braking
12025 Tech Center Drive, Livonia, MI 48150 USA
Phone +1 734 855-2755 Fax +1 734 855-2695
I found some clarifying statements from a Rego presentation:
So, this explains why when I removed all Java instances from my machine, it still worked (slowly) - as I had not removed the JRE folders/files under the CA Clarity PPM Schedule Connect folder.
Still stuck with same performance issues stated in previous reply. See that my screenshots didn't get added from log files. Sections from logs, below. Should be able enable other logs and get content Tuesday.
[error] [08/31/2015 1:41:15 PM] Export:
[error] [08/31/2015 1:41:15 PM] Merge feature is: DISABLED.
[error] [08/31/2015 1:41:15 PM] Total time to cache objects: 1.000000 seconds.
[error] [08/31/2015 1:41:15 PM] Objects cached:
[error] [08/31/2015 1:41:15 PM] TEAM: 19
[error] [08/31/2015 1:41:15 PM] CALENDAR: 19
[error] [08/31/2015 1:41:15 PM] OT_BASELINE_REVISION: 2
[error] [08/31/2015 1:41:15 PM] ASSIGNMENT: 26
[error] [08/31/2015 1:41:15 PM] PROJECT: 1
[error] [08/31/2015 1:41:15 PM] NOTE: 52
[error] [08/31/2015 1:41:15 PM] CONSTRAINT: 59
[error] [08/31/2015 1:41:15 PM] OT_BASELINE_DETAIL: 174
[error] [08/31/2015 1:41:15 PM] TASK: 140
[error] [08/31/2015 1:41:15 PM] RESOURCE: 30
[error] [08/31/2015 1:41:15 PM] Total time to write XML file(s): 4.000000 seconds.
[error] [08/31/2015 1:41:15 PM] Total time to open XML file(s): 50.000000 seconds.
[error] [08/31/2015 1:40:56 PM] HttpFieldlist::GetField(fieldName) not found. (fieldname = __MYTYPE__)
[error] [08/31/2015 1:40:56 PM] HttpFieldlist::GetField(fieldName) not found. (fieldname = UID)
[error] [08/31/2015 1:40:56 PM] HttpFieldlist::GetField(fieldName) not found. (fieldname = prProjectID)
[error] [08/31/2015 1:41:57 PM] Assertion fails in ..\caMspUtil\NkObjectManager.cpp at line 82
There are a couple of things Support can look further into, such as the issue regarding the lock not being released in Clarity. I've personally encountered the same scenario before and we were just discussing this today within the team about the same conditions for replication as you mentioned.
Can you do one test, once the slow project is opened in MSP, and the xml file is generated. Close the project without saving so that MSP doesn't have any project opened any more, then open the XML file, choose 'open as a new project' option when prompted by MSP. Time it and see if the time is roughly how long it takes for launching from Clarity. If possible could you try increasing the JVM allocation (TEC1743774) for scheduler to see if that makes a difference: regedit > HKEY_CURRENT_USER\niku\schedulers\MSPOptions add a new string value and name it JavaMemoryLimit, I have mine set to 1024 but it can be as much as your workstation can provide if discrimination against other applications is allowed .
About JAVA version, yes the new interface comes with its own and we did find that the JAVA_HOME system variables sometimes interfere with it, we're still working to narrow down the consistent steps to replicate it. A colleague and I tested a while ago and no you can't point XOG's java to MSP's to make XOG work, unfortunately.
We hope to come up with steps that consistently lead to replication for the above mentioend issues, therefore it would help us if these details are also reported into existing or new support cases. We will publish posts and if necessary update the CA WIKI information (have you tried asking a question or request for changes on the new DocOps platform on ca.wiki.com ? it's awesome!) with consistent information concluded from the cases to help more customers.
- 1:12 to open file (project ID PR28183) from CA PPM before and after JavaMemoryLimit change (set to 2048) – no difference observed
- 0:46 to open XML file from hard disk – seems consistent with numbers found in log
This particular project and its parent are typical for us,
- Parent consists primarily of milestones, not used for time entry
- Child has 4500 actual hours, primarily spread across two tasks from 18 resources
o we’ve not used WBS well, historically
o starting to improve, but we have many in-flight projects we must still deal with
o we have generalized ‘support’ projects that are much worse, but we may get away with just shutting these off and starting over
MSP field mappings are out of the box, and would not explain the difference in performance that I see vs. our app engineer (Grace).
I would like to understand if there is a way to determine which interface is installed on a user’s machine. When her export to MSP runs, she gets various pop-up windows appearing that remind me of the legacy version – but she insists that Support helped her install the XML version. By looking at VBA/Macros in MSP, is there something we can look at which identifies one installation from another?
Yes – have seen CA Wiki and have provided input there. Looks like it has great potential.
Grace and I are going to spend some more time on this, later this morning, including the log captures that you suggested earlier.
I normally check the Control Panel for the interface version.
Will check with our team here to review the details.
Control Panel\Programs\Uninstall or change a program just lists the names of the CA products installed, not the versions.
However, working with my app engineer, comparing VBA/Macros side by side between our machines I was able to determine that she had the legacy version installed. We know the legacy version works. She uninstalled, then installed the XML (x86) version and can now replicate the same issues that I’m having. So, unfortunately, we don’t have a situation where the XML version works for some and not for others – it’s not working for anyone.
We installed patch 5, yesterday, testing today:
- 1:30 to open parent PR31376 and its child PR28183
- After 4:27 saving parent/child back to CA PPM, still received “Save was not successful.”
- Upon closing MSProject, parent and child projects still locked in CA PPM
No change in performance resulting from patch 5.
I’ve attached debug log files from yesterday’s session. These are being sent to Support, as well.
Do you use a custom tool to monitor installed programs?
Here is what shows for my lab server on Windows 7 Enterprise 64bit; when the legacy driver is installed I'd see the word 'Legacy' in the name as well:
No custom tool to monitor installed programs.
I don't have a screenshot to back my words up. When our app engineer had legacy version installed, "legacy" did not appear in this view. We ended up comparing VBA/Macro content and I saw content their that referenced "dll" files from legacy and lacked references to "xml" files that my installation had.
One more thing, it would help to take a look at your field mappings, from the mspfields table.
Our MSP Mapping, below. Out of the box, no customer configuration performed, yet.
And, from MSPFIELD table:
The last one listed looks to be a custom one, it may have been previously added prior to the upgrade so it shows up automatically post upgrade. However you shouldn't have to worry about it for now since the issue with projects not opening at all was resolved and you're now working on performance with our team via existing cases.
Having too many custom mapped fields can contribute to performance (with old and new drivers), but in your case there is only one so that's not a cause. If you get a project failing to open and one of the logs point to you 'extendedAttribute', then we can revisit this custom mapping.
Hi Dale - Were you able to resolve your issue? Regards, Chris