Improve and reinforce salesforce training & adoption using WalkMe's digital adoption platform. Start saving on costly employee training by creating fast intuitive Walk-Thrus for Salesforce. Claim your Free Account Now
Course Of The Month
3 days, 9 hours left to enrollBecome a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Time Matters 11 in Windows 2008 Domain Environment
Posted on 2013-06-26
Dear Experts,
We are performing a migration from a Windows 2003 domain to a brand new Windows 2008 domain.
We performed the migration of 10 or so computers and tested. Everything is working perfectly except for the application Time Matters. We had to back out of the migration until we get this problem fixed.
Here is a summary of the problem and the troubleshooting we have done so far:
Problem: When we launch Time Matters (v11) we connect to the SQL database just fine. The application opens and it seems that it functions ok as well. However, at the same time the application opens, an error message also opens.
Of course, we go down the rabit hole of looking at the Support Article the error message references and ultimately says there is an issue with SQL (in brief).
When we close the application and close the error message two or three times, it finally leaves us with another error message:
Here is a summary of the troubleshooting we've done to determine that it is NOT a SQL related issue.
We do NOT have an active support contract with Lexis Nexis / Time Matters so cannot call them. I can't even buy a per incident support case.
Thanks for your help.
Mark
We are performing a migration from a Windows 2003 domain to a brand new Windows 2008 domain.
We performed the migration of 10 or so computers and tested. Everything is working perfectly except for the application Time Matters. We had to back out of the migration until we get this problem fixed.
Here is a summary of the problem and the troubleshooting we have done so far:
Problem: When we launch Time Matters (v11) we connect to the SQL database just fine. The application opens and it seems that it functions ok as well. However, at the same time the application opens, an error message also opens.
Of course, we go down the rabit hole of looking at the Support Article the error message references and ultimately says there is an issue with SQL (in brief).
When we close the application and close the error message two or three times, it finally leaves us with another error message:
Here is a summary of the troubleshooting we've done to determine that it is NOT a SQL related issue.
From the machine that has been migrated already to Windows 2008 (PC#1), we connect to the new database AND the old one and get the same message.
All of the other machines that are still on the old domain, connect to both databases - old and new - without an issue or error message
On PC#1, logged in with a brand new user account and let Windows create a brand new profile. Get the same error message on both databases
Unlinked all GPOs on the default domain policy on the new Windows 2008 domain. PC#1 has absolutely no GPOs being applied. Same error on both databases
Unjoined domain on PC#1, no error messages EITHER database
No firewall running and AV disabled for troubleshooting
We do NOT have an active support contract with Lexis Nexis / Time Matters so cannot call them. I can't even buy a per incident support case.
Thanks for your help.
Mark
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
-
4
3
7 Comments
I'm shooting totally in the dark on this so bear with me.
Do the same logins/users with matching SIDs exist on both sides?
A way to check is the sp_help_revlogin script.
http://support.microsoft.com/kb/918992
Is there a service running on the old server that is not on the new?
Is there a config file or registry entries that don't match?
Dump the registry to files and then use Beyond Compare (scootersoftware.com) to compare the files.
I'm guessing it is a userid/login issue that is masquerading as something else.
I do
Do the same logins/users with matching SIDs exist on both sides?
A way to check is the sp_help_revlogin script.
http://support.microsoft.com/kb/918992
Is there a service running on the old server that is not on the new?
Is there a config file or registry entries that don't match?
Dump the registry to files and then use Beyond Compare (scootersoftware.com) to compare the files.
I'm guessing it is a userid/login issue that is masquerading as something else.
I do
Thanks Jimpen,
Remember, computers on the OLD domain can use the application fine while connecting to the NEW database on the NEW server.
So, although I like your thinking, the configuration of the server, SQL or shared Time Matters application data folder, on not the issue.
The problem only starts to occur once the computer joins the NEW DOMAIN.
By the way, in my early troubleshooting I did use Beyond Compare to see the differences in the shared Time Matters application data folders. There are a number of INI files in there and everything is tip top. Good idea on the registry comparison, but again, cant be the problem or all computers would have a problem.
Thanks for your suggestions. Still working towards a resolution.
Yesterday I tried to update the SQL drivers on the client machines, to no avail.
Thanks,
Mark
Remember, computers on the OLD domain can use the application fine while connecting to the NEW database on the NEW server.
So, although I like your thinking, the configuration of the server, SQL or shared Time Matters application data folder, on not the issue.
The problem only starts to occur once the computer joins the NEW DOMAIN.
By the way, in my early troubleshooting I did use Beyond Compare to see the differences in the shared Time Matters application data folders. There are a number of INI files in there and everything is tip top. Good idea on the registry comparison, but again, cant be the problem or all computers would have a problem.
Thanks for your suggestions. Still working towards a resolution.
Yesterday I tried to update the SQL drivers on the client machines, to no avail.
Thanks,
Mark
That sounds like a SID issue then.
Is there a table in the database that has the computer names and or SIDs?
Is there a table in the database that has the computer names and or SIDs?
Featured Post
Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.
One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
Suggested Solutions
In-place Upgrading Dirsync to Azure AD Connect
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility.
Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
This Micro Tutorial hows how you can integrate Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease.
The following video show how to bind OSX Mavericks to …
Suggested Courses
Course of the Month3 days, 9 hours left to enroll
751 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.