Claim Digger

Hi,
I just installed Primavera 6 (P6) on my computer at work.
The tool, Claim digger wont work.
When I click on it, it seems to load just for a second and nothing happens.
I re-installed the program and it still did not work.
How can I get to work?
Thanks,
Edited by: user13317756 on Jun 23, 2010 6:13 AM

I cannot see how this is related to Database - Upgrade:
http://forums.oracle.com/forums/category.jspa?categoryID=247
Werner

Similar Messages

P6 Claim Digger Issue - access is denied

I couldn't use P6 claim digger since access is denied. I'm using P6.7 standalone version.
The following is error message.
an application event has been intercepted. ID 914162.1
event code: AID-3473-B
Type: EOleException
Description: Access is denied
Please let me know how to solve this. Thanks in advance.
Eddy

We are having the same issue. Here is the report it generates
I have found this that seems to point to the same issue, however not very helpful in resolving it.
http://www.linkedin.com/groups/Update-Baseline-additional-scope-without-906467.S.45554941
Any help at all would be awesome.
* EXCEPTION REPORT *
Date: 28-Dec-11
Executable: PM.exe
Application: Primavera P6 Project Management
Event Code: AID-3473-B
Message:
Access is denied
Context:
1: TfrmUsers.vqsUsersRowChange
2: TfrmUsers.DoPopupUsers
3: TfrmMain.actAdminUsersExecute
4: TfrmMain.actProjectsExecute
5: TCFormManager.SetToolbar
6: TfrmLogin.FormCreate
7:
8:
9:
10:
Detail:
Type: EOleException
Object Type: TfrmMain
System Info
===========
Username:*edited out* Hostname: edited out
OS Version: Windows NT ver 5.2, build 3790, Service Pack 2 (Intel Pentium)

Claim Digger Fix

i am having a problem when i try to run Claim Digger. i get an "An application event has been intercepted" Event Code TBREB-0670-3 error message.
i came across these posts:
Re: Claim digger event code 7cc307b6
Re: problem with client P6 install
which seemed to help them out. however, i have no idea what or where or how i would input:
*"according to note 913032.1 , i ran the following command and fixed the problem with importing.*
*INSERT into SETTINGS (namespace, setting_name, setting_value) values ('Administrator_Settings', 'JdbcConnectionURL', 'jdbc:sqlserver://FYITESTSVR:3574;database=PMDB_P6V7;'); "*
i am running P6 Project Management 7.0.0 Build: 92 with my Database being PMDB
thanks in advance,
Andre

Forget about that SQL statement below for now. The first two things I would look at are:
+"Event Code: TBREB-0670-3 When Updating Baseline or Launching Claim Digger. [ID 906605.1]"+
1.) Check your permissions on the client PC P6v7 is being launched from. If you are not a local administrator then you'll need full control of:
-\Common Files\Primavera Common\Java directory
-hkey_local_machine\Software\Primavera\CommonDir
+"Minimal Permissions To Folders And Registry Keys Necessary To Run P6 Version 7 (P6 v7) Client Applications [ID 1082738.1]"+
2.) Re-create the JRE configuration if you haven't already.
+"How To Change The Database Connection Information For Claim Digger/Schedule Analyzer For Project Management? [ID 899593.1]"+

Claim Digger in P6

When I used Claim Digger for P3, I was able to see the
number of activities that missed their start or finish.
The new, "integrated" versio in P6 is missing this
feature. Your knowledgebase indicates that this is an
"enhancement request". My question is this - if it existed
previously, how is it an enhancement? Is this a case of
Primavera "dumbing down" the software so that they can
turn around and $ell it to me later? What a waste.

Hi,
Thanks for taking the time
to share your concern about the integrated version of
Claim Digger. The intent is not to "dumb down" the
software so we can sell more of it. Part of the issue
here is that Claim Digger for P3 was built on
technology that wasn't compatible with P6. This meant
we needed to re-code Claim Digger for P6. During this
process we tried to strike a balance between bringing
the core functionality to users quickly in P5 and P6
against against ensuring every feature from P3 made it
into the software.
I'm sorry
the functionality you enjoyed in the P3 version of
this tool isn't currently available. Enhancing the P6
version of Claim Digger will be considered along with
other P6 enhancements in the future. If you haven't
done so already, please click the link on the solution
asking that you be added to the enhancement request so
we can accurately track the number of customers who
want to see this feature included in future iterations
of the tool.
Sincerely,<br
/>Sean James

Claims Digger report - values for changes in duration/float/lags

When I compare two projects using Claims Digger, I always get results for changes in durations, float and lags in hours as opposed to days? Is there a setting that can fix this?
Please advise.
Thanks!

I think (not 100% sure) P6 is working as designed.
The basic unit of comparison in P6 is hours and not what is set in user preferences.
For example when you run a global change the basic unit used in calculations is hours.
Also when we enter duration in days, its actually been stored in database in hours and then converted to days using activity calendar in P6v7.
Jawad

Primavera P6v7 use with Claim Digger

I'm having trouble getting Claim Digger to work correctly. Is Claim Digger only associated with the PMDB database or can I create other databases within primavera and have claim digger work?
Thanks for any help.

Try the following:
1. Look for the admin.cmd file, which is usually in C:\Program Files\Common Files\Primavera Common\Java\admin.cmd
2. Run admin.cmd
3. Login as privuser.
3. In the Database section of your current configuration, change the name of the database for the Instance 1 Database URL.
4. Click on "Save Changes" at the bottom right.
5. Log back into Project Management and run Claim Digger
Hope this helps!

Unable to access claim digger in P6 Professional R8.3.2

Hi
I cannot access claim digger in P6 Professional R8.3.2. The programme shows the following message:
The selected application: c:\progra~1\java\jre1.7.0_15\bin\javaw.exe cannot be found.
How could this problem be solved?
Thanks

Hi,
P6 will use JAVA application to run Claim Digger. Based on the error, P6 cannot find the JAVA set in the JAVA_HOME to run javaw.exe. Please set the right JAVA_HOME variable in the environment variable so P6 can find Java and then run claim digger,
Regards,
Pablo
========
Was our answer helpful?
If so, highlight the information for other Community members by rating it or marking the answer as correct.
Just hit the “Correct Answer” link on the answer, or rate it by clicking "Helpful Answer" or "Like".

P6's Claim Digger vs original Claim Digger

Is the P6v7.0's Digger report static? Is it possible to alter the report in anyway, sort by Activity ID ascending, for example?
Will it export to Word or Excel?
Being relatively new to P6, I haven't spent a much time with it.
Hopefully the report's formatting and flexibility is better than what I've seen so far.
I bought the original Claim Digger 10 years ago for P3 comparisons; before Primavera bought it from HST. Great product. Invaluable.
Thanks!

keithc,
Claim Digger is a great tool for what it was designed for. Our version of CD in P6.7 has not been operational for a while due to an IS issue but we miss it often. It's like having your own data wizard in a box.
CD is able to export to MS Word or Excel. Also, the complete data analysis of a wide variety of changes is available in a text file for custom reporting.
Hope this info helps,

Trouble in Claim Digger

Hi, i am not able to run claim digger in P6.2. the error message says " unable to access jarfile C:/" can anybody guide me on what to do?

Hi,
Normally the error would be more like "Unable to access jarfile C:\Program Files\Primavera\Project Management\Claim Digger\prm-cd.jar when launching Claim Digger"
If that is the fill error message you are getting then it is just because it is looking for a folder called Claim Digger that is currently named Schedule Comparison. To fix this you just need to rename the folder Schedule Comparison to Claim Digger.
If the error message you are getting is cut off at C:\ then it is possible that the registry entry is currently incorrect.
I only have P6r8 and they have changed the registry for this area of the product but you should be able to go to Regedit and go to
HKLM\Software\Primavera (if you are on a 64bit operating system then it will probably be HKLM\Software\Wow6432node\Primavera).
Hunt through the subfolders and there should be one in there called Claim Digger that has a parameter for the location of the jar file - set this to the same as the path's i've shown above (confirm exactly which one you have currently).
After that change is made, start P6 again and try claim digger again.
Regards
Alex

P6 Claim Digger

Hi, How do I locate the Claim Digger file that is created in P6. Everything seems to run OK, but the file does not appear on the screen or cannot be found on the computer?

user11865676 wrote:
Hi, How do I locate the Claim Digger file that is created in P6. Everything seems to run OK, but the file does not appear on the screen or cannot be found on the computer?When you run Claim Digger and save the output it asks you where you would like to place it.
If you are accessing P6 via Citrix, you will need to make sure you save it to a mapped network drive you have access to outside of the Citrix session.

Claim Digger Report

When viewing the report produced by Claim Digger, under the heading bold "General Realtionship Differences" bold, the report shows a Predecessor Activity Name and a Successor Activity Name. Is the report referring to each activity being related to each other, or is there a 3rd activity that has the listed ones as the respective Predecessor and Successor.
Actually is there anywhere a guide that lists the components of the Claim Digger report and how to read them all correctly? Most of it is fairly straightforward I know, but some areas can be a little bit grey.
Regards,
buffhunt.

Hi Douglas,
As you might have found out these reports can be huge. So try and filter down to the smallest amount of data to be compared.
The documentation that you will need for Claim Digger can be found in the Project Management Reference Manual.
You can also try reading Part 4, "Updating and Managing the Schedule".
Also try looking on the "Documentation" CD that came with your software.
Hope this has helped you.

Claim digger event code 7cc307b6

Wnen trying to open Claim Digger from P6.7 I get the following error message. "Event has been intercepted. event code 7CC307B6".
Have submitted four service requests over the past two days to no avail. Not a fan of the new Oracle system.
Any thoughts appreciated. Thanks.

i have the same problem also
i m trying to search in the Oracle site but no hope i really dont like the new oracle issue
in the past we used to search in primavera knolege base and there was screen shoots for the solutions even if we couldnt find it we used to call the support
but now there is nothing
hope some one solve this issue for me
thanks

Claim Digger's "General Relationship Differences" - What's the meaning?

When I run the Claim Digger report and look at the section "General Relationship Differences", it list out a long list on new & old predecessors even though NONE of the listed activities have changed their predecessor, NONE! What is this section refering to?

When I run the Claim Digger report and look at the section "General Relationship Differences", it list out a long list on new & old predecessors even though NONE of the listed activities have changed their predecessor, NONE! What is this section refering to?

Claim digger not working on P6 v7 SP1

I have used claim digger fairly regularly but suddenly has stopped working. Ever since I upgraded to v7 SP1 It has not worked. Anyone else had this problem
Regards

While my experience with V.7 is quite limited I have seen this in V.6 as well. It is generally a combination of things that resolves the problem some of which you may need IT assistance with if this is not a stand-alone database.
1.) Delete C:\Program Files\Common Files\Primavera Common\Java\BREBootStrap.xml
2.) Run C:\Program Files\Common Files\Primavera Common\Java\dbconfig.cmd and create a new configuration. (requires DB connection info and pubuser password)
3.) Run C:\Program Files\Common Files\Primavera Common\Java\admin.cmd and delete all existing configurations except the new one created in step 2. (requires privuser password)
4.) Run C:\Program Files\Common Files\Primavera Common\Java\dbconfig.cmd and create a new configuration. Assuming you deleted the "Primavera Configuration" in step 3 it should automatically name it this.
5.) Run C:\Program Files\Common Files\Primavera Common\Java\admin.cmd and delete the configuration you created in step 2.
6.) Open P6v7 and attempt to launch Claim Digger. Note that sometimes I have seen it open up behind the client app and have had to alt-tab to bring it to the front.
7.) If it now launches but prompts for a password you should be able to type in your information and connect. To prevent it from asking for a password in the future I have had to do the following:
a.) reset your P6 password to blank (as in no password).
b.) logout and back into P6 with no password.
c.) launch Claim Digger and it should open without prompting for a password.
d.) reset your P6 password back to whatever it was.
e.) logout and back into P6 with your changed password.
f.) test claim digger.
Note that these are the steps I use to resolve this in V.6. As we do not yet run V.7 I do not know if everything is the same.
Edited by: ARE_DC on Apr 20, 2010 7:10 AM

Unable to export Primavera P6 xml files

Hi there,
Good day. I have some issues during the import/export process. For some unknown reason, Primavera generates blank xml files during the export process. I chose Primavera P6 - (XML) as export file format. Here are the steps that I have followed
-- Open a project
-- Click on file and then on Export at the main menu
-- Choose XML as export format and specify the file name path
-- Click Finish
-- Primavera generates a blank xml file instead of a zip file which primavera would normally do.
Has anyone of you run into this kind of problem?
Many thanks in advance.

Hi,
I mention you're using the p6 professional / P6 Client. Which version/Release (P6v7.0, R8.0, R8.1, R8.2 or R8.3) with which Service Pack do you use?
Can you first check if the Claim Digger/Schedule Comparison is working? If not can you please check which JRE you have installed and if you have a environment variable JAVA_HOME set to your JRE-path.
Regards,
Daniel

Claim Digger

Similar Messages

Maybe you are looking for