"InstallShield error ####: Unable to install InstallShield Scripting." appears when running Setup of AutoAAP v.10.
The message "Setup failed to configure the server…" appears when running Setup.exe.
"You have insufficient database access privileges." message appears when starting AutoAAP. Or the Database Connectivity dialog box appears, but if MSDE is selected, the Test Connection fails.
In container Stage 6 Check Container Steps an error appears about missing EEO Codes. Also, in container Stage 7 Edit/View/Export several employees have a blank EEO Code field.
The error "Application has generated an error that could not be handled" appears when attempting to print or preview any report that uses Final Availability data (Availability Analysis, Incumbency v Availability, Placement Goals).
The Compensation Analysis Report shows very large salaries, several times higher than those shown in the Employee data.
In the Work Force Analysis report, some job titles show a Salary instead of a Pay Grade, even though Pay Grade is the selected ordering field in the report’s Properties screen. The Job Title may be shown twice, or it may be shown just once.
"The Import Failed. Error Importing Data." Message appears when trying to import a file.
The following message appears when attempting to run the AutoAAP Setup.exe program: "This patch could not be opened. Verify that the package exists and that you can access it..."
 |
"InstallShield error ####: Unable to install InstallShield Scripting." appears when running Setup of AutoAAP v.10. |
 |
Cause & Solution: Common causes include:
- Setup was started previously and cancelled. This can leave portions of the setup program in memory. The solution is to restart Windows, which will clear the computer's memory. Now restart Setup for AutoAAP v10.
- Other programs may be running that can interfere with the Setup program. Disable antivirus software and other applications.
- The version of InstallShield used by AutoAAP v.10 requires Internet Explorer version 5.5 (SP2) or later. To check your version, start Internet Explorer. Select Help at the top of the screen, and then select About Internet Explorer. The version must be 5.5 or higher.
- Your Windows logon has insufficient permissions to install software. Make sure your logon has full administrative privileges on your computer. This applies to Windows NT 4.0, 2000, and XP computers.
|
|
|
The message "Setup failed to configure the server…" appears when running Setup.exe. |
|
Cause & Solution: Setup is trying to install Microsoft SQL Server Desktop Engine (MSDE) when an instance of MSDE already exists or a previous installation of MSDE was not completely removed. Use Add/Remove Programs in Control Panel to remove MSDE, and then run Setup.exe again. If MSDE has already been removed, then delete the contents of the folder C:\Program Files\Microsoft SQL Server\Data, then run Setup.exe again. |
|
|
"You have insufficient database access privileges." message appears when starting AutoAAP. Or the Database Connectivity dialog box appears, but if MSDE is selected, the Test Connection fails. |
|
Cause & Solution: Your Windows logon does not have Admin privileges and AutoAAP was not run one time while using an Admin logon. Restart Windows and logon with a username that has Admin privileges, then run the Database Installation option on the Start – Programs menu under Biddle Consulting Group – AutoAAP 10. This will create the initial configuration files. AutoAAP may now be run using a Windows logon that does not have Admin privileges. |
|
|
In container Stage 6 Check Container Steps an error appears about missing EEO Codes. Also, in container Stage 7 Edit/View/Export several employees have a blank EEO Code field. |
|
Cause & Solution: This can occur for a few reasons:
- All employees in the imported Employee file that have the same job title have no EEO code assigned.
One option is to modify the import file to give employees in this job title an EEO code, then re-import the file. Or you can go ahead and complete the Plan Container stages, including Stage 5 Create Plans/Link Data to Plans, then proceed to Plan Stage 1 Job Titles/Census Codes. Any job title without an EEO code will appear in the list under Not Yet Assigned to an EEO Category. Click to select the target job title, and then select an EEO Category on the right side of the screen.
- Multiple employees in the imported Employee file have the same job title but have different EEO codes.
If the same job title appears more than once in the imported Employee file, but with different EEO codes, then the job title will be unassigned from any EEO code. A job title may have only one EEO code. Either modify the import file and re-import employees, or complete the Plan Container steps, including Stage 5 Create Plans/Link Data to Plans, then proceed to Plan Stage 1 Job Titles/Census Codes. The target job title will appear in the list under Not Yet Assigned to an EEO Category. Click to select the target job title, and then select an EEO Category on the right side of the screen.
- A record in one of the transaction files has a unique Job Title - When a job title appears in one of the transaction files but does not appear in the Employee file, it will have no EEO code, since EEO codes come from the Employee file. This can occur in three cases:
- The job title is new, applicants have applied, but no hire has been made. In this case, the job title will appear in the Applicant file but not in the Employee file.
- An employee has been terminated from the job title, and no other employee currently holds that job title. In this case, the job title will appear in the Terminations file but not the Employee file.
- An employee has been promoted from the target job title to another job title, and no other employee currently holds the former job title. In this case the job title will appear in the Promotions file but not in the Employee file.
Correct this in Plan Stage 1 Job Titles/Census Codes, by assigning job titles listed under Not Yet Assigned to EEO Category to their appropriate EEO Categories.
|
|
|
The error "Application has generated an error that could not be handled" appears when attempting to print or preview any report that uses Final Availability data (Availability Analysis, Incumbency v Availability, Placement Goals). |
|
Cause & Solution: This error can occur for a variety of reasons having to do with insufficient RAM, or incomplete or corrupted Availability data. The most common causes are:
- Your computer has insufficient memory (RAM). If no other programs are running, 128 MB of RAM may be sufficient to run a Desktop installation of AutoAAP v.10, but the program will perform better on computers with 256 MB of RAM or more. If any other programs will be running at the same time as AutoAAP, then more RAM is recommended.
- In Plan Stage 3 Labor Areas, a defined Labor Area (listed under Labor Area Assignments) has been assigned to both Local and Reasonable for the same Job Group. A defined Labor Area may only be assigned to one component for a Job Group, either Local or Reasonable, but not both. This can be corrected in Plan Stage 3 - Labor Areas by removing the unneeded labor area from the affected component.
- In Plan Stage 6 Final Availability, a component (Local, Reasonable, National, Feeders) has weight applied but has zeros for all gender and ethnic groups. This usually indicates that no census data could be found within the defined labor area for the census code(s) assigned to one of the job titles within the job group. An example would be if Census Code 135 Chemical Engineers is assigned to a job title, but the Census contains no data for that occupation code within the defined labor area. The solution is to use a different Census Code or expand the defined labor area to include additional Census areas.
- The is a job group with no employees in it. This will show up in Container Stage 2 Job Groups. Each job group listed on the right side of the screen has the number of employee in parentheses to the left of the job group name. If a job group has zero employees, delete it. No planning is performed for a job group unless there are currently employees in the group.
|
|
|
The Compensation Analysis Report shows very large salaries, several times higher than those shown in the Employee data. |
|
Cause & Solution: There are two common data issues that can cause this.
- Annual salaries are listing in the Salary field in the imported employee file, but the Wage Type used is not Annual. AutoAAP multiplies the salary field contents by a multiplier that corresponds to the Wage Type. If the Wage Type is Monthly, for example, then the Salary field contents will be multiplied by 12 to derive the annual salary amount. There are three ways to correct this:
- In Plan Stage 7 Edit/View/Export, change the Wage Type to Annual for the affected employees. Use the View Single option to change an employee's data.
- In Container Stage 4 Wage Types/Pay Grades, change the multiplier for the problem Wage Type to 1. This will cause the Salary field contents to be multiplied by 1 to derive the annual salary. Do this only if all employees using the problem Wage Type have annual salaries in the Salary field.
- In Container Stage 3 Map Data, map the Monthly source code to Annual in the Destination Code list. This will cause AutoAAP to treat all Monthly wage types as annual. Do this only if all employees using the problem Wage Type have annual salaries in their Salary field.
- Some of the employee salaries are corrupt. To check this, use Edit/View/Export Data to look at the Employee file. Select View All and look for a Salary field that has more than two decimal positions, such as: 10,135.65000. To correct this, click on the target employee record and select View Single. In the salary field, re-enter the right-most digit in the salary. Select View All and verify that the salary now has no more than two decimal places showing. Correct all Salary fields that show more than two decimal places.
|
|
|
In the Work Force Analysis report, some job titles show a Salary instead of a Pay Grade, even though Pay Grade is the selected ordering field in the report’s Properties screen. The Job Title may be shown twice, or it may be shown just once. |
|
Cause & Solution: This occurs if employees within the same Job Title, within the same Organizational Unit, have different Pay Grades. The solution is to assign the same Pay Grade to all employees within a Job Title, at least within the same organizational unit. |
|
|
"The Import Failed. Error Importing Data." Message appears when trying to import a file. |
|
Cause & Solution: This error is typically the result of invalid date information within the file being imported. This may be an invalid date (such as 02/05/2009 or 05/00/04), or multiple date formats within the same file (such as mm/dd/yy and m/d/yyyy). Be sure all date fields are formatted the same within the file being imported, and that all dates are valid. |
|
|
The following message appears when attempting to run the AutoAAP Setup.exe program: "This patch could not be opened. Verify that the package exists and that you can access it..." |
|
Cause & Solution: This is a Microsoft error message related to possible corruption in the computer's registry:
- Your computer's registry has become corrupted.
- You or someone else inadvertently changed a registry setting that is used by Windows Installer and that is causing a problem.
- The installation of a program that uses Windows Installer was interrupted.
- There are multiple instances of Setup running at the same time, or an instance of Setup is "blocked."
Microsoft suggests using their Windows Installer Cleanup Utility, available at the following site, along with instructions:
Try rebooting the computer first, and make sure the Windows Logon in use has Administrator privileges required to setup software.
|
|
