Ouch. Time to increase buffer size!
Note: You may need an IT person to access the Registry.
To change the MaxLocksPerFile Registry setting:
1. Go to START, the RUN, type REGEDIT, click OK. Registry editor should open.
2. Open Hkey_Local_Machine\software\Microsoft\Jet\4.0 folder.
3. Double-click the MaxLocksPerFile entry on the right. An edit dialog box should open.
4. Click the Decimal radio button. Default is 9500 (in decimal)
5. This step is trial and error, start with a value of 50,000 then reimport. If you get the error again go back in and up the value. We had to take it to 1,000,000.
Hope this helps!
Wednesday, May 11, 2011
Recalculation options
These are good defaults for a recalculation. DO NOT USE THE DEFAULT SETTINGS. The have caused me many problems.
Data not showing up in wInsight, Administrator OK.
If there is data in Administrator and it's not showing up in regular wInsight do a simple recalc BUT only for the period. Double click on the contract name to get all the periods to jump up instead of . Highlight the period and be sure to only select Sum from lowest levels and Calculate element hierarchy. If you need future period data then select that too. Do not select future period data if you receive that already, you'll jack up the contract permanently and need to do delete/re-imports. Which suck.
Re-importing periods with incorrect data
I recently found out one of my databases has been updating wrong. Loooong before I took over the database. I found a discrepancy between the WBS and OBS numbers. Of course, WBS and OBS should always be the same. What's funny is that all the periods back to July 2010 were messed up. My team and I tried to delete/re-import these periods in order, i.e. Jul 10, Aug 10, Sep 10 etc. The data was still incomplete. So then we tried it backwards. We started with Mar 11 and deleted/re-imported. Without a recalc the numbers were good. We then did Feb 11, Jan 11 and the numbers came out great. After all periods were done we did a full contract recalc (took all night) and the numbers matched across the board.
PLUG info from the experts
Why are there PLUG elements in the Work Breakdown
Structure?
Question
Why are there PLUG elements in the Work Breakdown Structure?
Answer
PLUG elements are generated by wInsight Administrator during the import of a transfer
file.
A PLUG element is an anonymous element whose sole purpose is to maintain data that
once existed at what is now a summary level element.
Background: It is important to understand that all data is input in wInsight at the lowest level.
Example: WBS 3200 is a level 3 element when the contract was started.
For the first six months, this element was routinely updated for earned value.
In the seventh month, it was decided to expose more detail below this element by
adding WBS elements 3210, 3220, and 3230.
This changes WBS 3200 from a child (lowest level element) to a parent.
Element 3200 can no longer be visible in the input screen because it is a parent, not
a child.
The question is, what happens to the sixth months worth of data?
In this case, wInsight creates an anonymous element called PLUG for the purpose of
retaining the past history when data was entered for WBS 3200. Some users make the
mistake of deleting this PLUG element because there is no data for it in the seventh
month. However, by deleting this element, you erase all the prior history data that was
once entered in WBS 3200, which is now PLUG. In some cases, the PLUG element can
be deleted because the element that it represents never had data input in the first place.
Resolution: It is our recommendation that PLUG elements be dealt with in two ways:
Option #1: If there is any historical data in the PLUG element:
1. Open the Elements table under Contract Setup.
2. Rename PLUG to some logical WBS Number in that part of the WBS tree.
3. Also, rename the Sort value as well.
Note: Retaining the PLUG identity may cause difficulties later on should the PLUG become a
parent of another PLUG.
Option #2: If you can verify and be absolutely certain that no data has ever existed in the PLUG
element even going back to the first period of data input, then you can delete the PLUG element
in the Elements table.
Important Note: Naturally, before deleting anything, always create a Backup file.
Structure?
Question
Why are there PLUG elements in the Work Breakdown Structure?
Answer
PLUG elements are generated by wInsight Administrator during the import of a transfer
file.
A PLUG element is an anonymous element whose sole purpose is to maintain data that
once existed at what is now a summary level element.
Background: It is important to understand that all data is input in wInsight at the lowest level.
Example: WBS 3200 is a level 3 element when the contract was started.
For the first six months, this element was routinely updated for earned value.
In the seventh month, it was decided to expose more detail below this element by
adding WBS elements 3210, 3220, and 3230.
This changes WBS 3200 from a child (lowest level element) to a parent.
Element 3200 can no longer be visible in the input screen because it is a parent, not
a child.
The question is, what happens to the sixth months worth of data?
In this case, wInsight creates an anonymous element called PLUG for the purpose of
retaining the past history when data was entered for WBS 3200. Some users make the
mistake of deleting this PLUG element because there is no data for it in the seventh
month. However, by deleting this element, you erase all the prior history data that was
once entered in WBS 3200, which is now PLUG. In some cases, the PLUG element can
be deleted because the element that it represents never had data input in the first place.
Resolution: It is our recommendation that PLUG elements be dealt with in two ways:
Option #1: If there is any historical data in the PLUG element:
1. Open the Elements table under Contract Setup.
2. Rename PLUG to some logical WBS Number in that part of the WBS tree.
3. Also, rename the Sort value as well.
Note: Retaining the PLUG identity may cause difficulties later on should the PLUG become a
parent of another PLUG.
Option #2: If you can verify and be absolutely certain that no data has ever existed in the PLUG
element even going back to the first period of data input, then you can delete the PLUG element
in the Elements table.
Important Note: Naturally, before deleting anything, always create a Backup file.
Tuesday, March 29, 2011
Import failed after Euwt links
Quick fix if your import fails after the Euwt links section.
Import the file again but select Options first. In the Options menu uncheck the Thresholds and Weights box. It will import fine. FYI- We use this fix only on contracts that we don't use Thresholds and Weights on or as a quick fix before we can get a clean .wsa file in. All data will be imported fine.
Import the file again but select Options first. In the Options menu uncheck the Thresholds and Weights box. It will import fine. FYI- We use this fix only on contracts that we don't use Thresholds and Weights on or as a quick fix before we can get a clean .wsa file in. All data will be imported fine.
Editing XML files over 512mb : gVim
My wInsight team has to constantly remove old PLUGs from XML files in order to get them to import properly. Usually we import the file, when it fails from a PLUG we note the PLUG number,open the XML in notepad, Ctrl-F to find the PLUG, delete the plug from element to /element, save as another name and then import that file. Usually it runs fine or runs into another PLUG. We do the same for the next PLUG. If it fails for something other than a PLUG after the PLUG have been removed we then import the ORIGINAL xml file and it goes through great. Recently we ran into a different problem. An .xml file over 512mb, specifically 1.12gb.
I tried editing in Notepad, MS XML Editor, IE, MS Word, and installed and tried Notepad++. Notepad supposedly had a 2gb threshold. Not so, s'pose it was wishful thinking or done on a top of the line 'puter. Luckily I found a program that can handle the large .xml files and is free: gVim. You can download it here:
ftp://ftp.vim.org/pub/vim/pc/gvim73_46.zip Easy interface and very simple, which means fast. I found it HERE.
I also tried XML Marker which seemed to work in the beginning but had problems 'parsing' the file and saving it. Cream, which is similar to gVim looked extremely promising but took longer to load. The stripped down gVim worked great.
I tried editing in Notepad, MS XML Editor, IE, MS Word, and installed and tried Notepad++. Notepad supposedly had a 2gb threshold. Not so, s'pose it was wishful thinking or done on a top of the line 'puter. Luckily I found a program that can handle the large .xml files and is free: gVim. You can download it here:
ftp://ftp.vim.org/pub/vim/pc/gvim73_46.zip Easy interface and very simple, which means fast. I found it HERE.
I also tried XML Marker which seemed to work in the beginning but had problems 'parsing' the file and saving it. Cream, which is similar to gVim looked extremely promising but took longer to load. The stripped down gVim worked great.
Subscribe to:
Posts (Atom)