Issue
Error - "The user ID is not associated with a PDK User ID." occurs when launching PS Time and Expense (PSTE).
Resolution
1. Confirm that each of the ODBC DSNs are defaulted to the correct default database.
Navigate to Start | Settings | Control Panel | Administrative Tools | Data Sources (ODBC), and verify that each of the DSN's you created is pointing to the correct database. You should have a DSN for each company database, one for the DYNAMICS database, one for the GPFramework database, and one for the GPTimeExpense database. Once you have verified that the DSN's are pointing to the correct location, the next step will be to verify that the correct DSN was selected during the install of PS Time and Expense. To do this, log into eBusinessDesk Administration. Go to Tools | Update ODBC Data Source. Go through the application names and make sure that the correct ODBC Data Source has been selected.
DYNAMICS --> DSN should have the DYNAMICS database as the default database.
PS Time --> When the data source type for Application is marked, the data source displayed should point to the GPTimeExpense database. When the company data source type is selected, it should point to the company.
PS Expense --> When the data source type for Application is marked, the data source displayed should point to the GPTimeExpense database. When the company data source type is selected, it should point to the company.
eBusinessDesk --> DSN should have the GPFramework database as the default database. If any of them are incorrect, select the appropriate data source to correct.
2. Make sure this user is set up in eBusinessDesk Admin in the PS Expense User Group and PS Time User Group.
3.Verify this user can create Timesheets in PDK and if not complete the PDK setup.
4. If a Windows 2003 server is being used install the Windows 2003 compatible version of eBusiness Desk 1.3 and PS Time and Expense. Version R7.5 extensions SP1 and SP2 of PS Time and Expense is the only versions compatible with Windows 2003 server.
This article was TechKnowledge Document ID:31877
Error - "The user ID is not associated with a PDK User ID." occurs when launching PS Time and Expense (PSTE).
Resolution
1. Confirm that each of the ODBC DSNs are defaulted to the correct default database.
Navigate to Start | Settings | Control Panel | Administrative Tools | Data Sources (ODBC), and verify that each of the DSN's you created is pointing to the correct database. You should have a DSN for each company database, one for the DYNAMICS database, one for the GPFramework database, and one for the GPTimeExpense database. Once you have verified that the DSN's are pointing to the correct location, the next step will be to verify that the correct DSN was selected during the install of PS Time and Expense. To do this, log into eBusinessDesk Administration. Go to Tools | Update ODBC Data Source. Go through the application names and make sure that the correct ODBC Data Source has been selected.
DYNAMICS --> DSN should have the DYNAMICS database as the default database.
PS Time --> When the data source type for Application is marked, the data source displayed should point to the GPTimeExpense database. When the company data source type is selected, it should point to the company.
PS Expense --> When the data source type for Application is marked, the data source displayed should point to the GPTimeExpense database. When the company data source type is selected, it should point to the company.
eBusinessDesk --> DSN should have the GPFramework database as the default database. If any of them are incorrect, select the appropriate data source to correct.
2. Make sure this user is set up in eBusinessDesk Admin in the PS Expense User Group and PS Time User Group.
3.Verify this user can create Timesheets in PDK and if not complete the PDK setup.
4. If a Windows 2003 server is being used install the Windows 2003 compatible version of eBusiness Desk 1.3 and PS Time and Expense. Version R7.5 extensions SP1 and SP2 of PS Time and Expense is the only versions compatible with Windows 2003 server.
This article was TechKnowledge Document ID:31877