Problem: "Error 1719. The Windows Installer service could not be accessed." This error typically would occur when trying to install software.
Cause: The Windows Installer files on your hard drive are damaged or are missing.
Solution: See article 315346 at Microsoft.com for instructions on re-registering Windows Installer.
Problem: The import process stalls on the Reading Headers process.
Cause and Solution: The most common problem is that the spreadsheet is password protected. Remove the password protection on the spreadsheet, and then try import again.
This can occur if the SQL SERVER permissions are incorrect for the database being accessed by AutoAAP Clients.
Transaction dates (Beginning and Ending) are set in the Data Container properties, and can only be modified there (Edit Data Container screen).
Click on the desired data container to display the Edit Data Container screen. Click in the data segment to be changed and type in the desired entry.
Once the dates are modified, the data must then be transferred again, using Transfer Data (Data Container stage 6). The modified dates will now appear elsewhere in the appropriate stages or report screens.
Issue: Some counties do not appear in the list of counties in the Plan Stage 3 Labor Areas, in the Create function.
Cause: Some county data sets caused a disclosure problem with an MSA/PMSA. When a problem existed, a decision was made whether to eliminate the MSA/PMSA or reaggregate counties. Most MSA/PMSAs were kept and are shown in the file. However, there are seven that were eliminated by the Census Bureau due to disclosure concerns.
Following are the seven MSA/PMSAs that will not show on the EEO File:
- Arizona: Flagstaff AZ-UT MSA - FIPS MSA Code #2620
- Arkansas: Fort Smith AR-OK MSA - FIPS MSA Code #2720
- Maryland: Baltimore MD PMSA - FIPS PMSA Code #0720
- New York: Newburgh NY-PA PMSA - FIPS PMSA Code #5660
- North Dakota: Grand Forks ND-MN MSA - FIPS MSA Code #2985
- Pennsylvania: Pittsburgh PA MSA - FIPS MSA Code #6280
- Wisconsin: La Crosse WI-MN MSA - FIPS MSA Code #3870
Problem: "Error 1719. The Windows Installer service could not be accessed." This error typically would occur when trying to install software.
Cause: The Windows Installer files on your hard drive are damaged or are missing.
Solution: See article 315346 at Microsoft.com for instructions on re-registering Windows Installer.
This can occur if the SQL SERVER permissions are incorrect for the database being accessed by AutoAAP Clients.
Problem: "A problem has occurred in the AutoAAP application: Column 'Name' does not belong to table Table."
Cause: The error indicates that the database and the client application are not in sync. Possible issues are:
- A non-current version of the client is in use, but a new database script was run.
- A new version of the client was installed, but a new database script was not run.
- A new database script was run, but permissions were not set properly on the stored procedures for the database user.
Solution: Make sure the version of the database is correct (matches the AutoAAP application), and that permissions to run stored applications are granted to the username/password setup for the database.
This can occur if the SQL SERVER permissions are incorrect for the database being accessed by AutoAAP Clients.
If the SQL SERVER permissions are incorrect for the database being accessed by AutoAAP Clients, a variety of problems can occur. These can include:
- Errors when trying to run reports ("There is an error initializing this report").
- Problem re-importing data with Overwrite option. Only Append will be allowed regardless of selection made.
- Errors in Job/Job Groups stage when Assign Jobs is used with an external Job file.
Problem: In the Zip Code Analysis table, the Total Count is less than the total number of imported applicants (or employees if they were used for the analysis).
Cause: The imported applicant data (or employee data) contains invalid zip codes.
Solution: As of January 2007, zip codes can be checked for validity at the web site:
http://zip4.usps.com/zip4/citytown_zip.jsp. Check the zip codes in the imported data to find the invalid ones and correct them.
|
