Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Teamserver issues after migration
23-Jan-2017, 02:48 PM (This post was last modified: 23-Jan-2017 02:54 PM by Sherman.)
Post: #1
Teamserver issues after migration
While migrating our development environment to a new server, we elected to copy our application and bizflow databases from our test enviroment. Teamserver lives separately on a Windows server whereas our bizflow/webmaker environments are on Solaris.
After copying our data, teamserver sees all of our connection attempts as "new users" and complains that connecting would result in a duplicate key for USER_USERNAME_UN on USER. (attached image) I assume this is in some custom data store that belongs to TS. Is there some way to recover from this situation without having to completely reinstall Team Server?

we are on BF12.3/Webmaker 7
Find all posts by this user
Quote this message in a reply
23-Jan-2017, 05:11 PM
Post: #2
RE: Teamserver issues after migration
Hi Sherman,

I'm sorry you are having issues with the Team Server connection.

I can't see the picture you mention in your post. Are you able to provide it?

Can you also clarify which components you have moved? Is the Team Sever still running in the same location, with the BizFlow installation moved to a new environment?

When you connect to the Team Server it communicates with BizFlow to check your user details, and then maps this information to an internal TS user representation.
One possible cause could be that the user ID values within BizFlow have changed, and so this mapping step is failing.

Are you able to try turning on some additional logging for the Team Server to help understand the situation?
If so, could you please edit the .../<Tomcat>/webapps/bfwmteamserver/doc/morphyc.xml file, and change the log="false" attribute on the <development_logging> element to be log="true".
Once this has been changed, restart the Tomcat instance running the Team Server, and try and connect from the Studio again.

It would be great if you could then send through the .../<Tomcat>/webapps/bfwmteamserver/doc/teamserver_log.txt file, the cas.log file from the Tomcat root directory, and any recently changed files from within .../<Tomcat>/logs.

In addition, it would be very useful if you are able to send through a zipped up copy of the <Team Server Data Location>/teamserver-db directory. This contains the database information that the Team Server uses to manage users and project state.
You can send any details vie email if you'd prefer (support@hyfinity.com), rather than posting on the public forum.

Hopefully this will help explain what the actual issue is, and indicate the best way to resolve this for you.

Regards,
Gerard
Find all posts by this user
Quote this message in a reply
23-Jan-2017, 08:37 PM
Post: #3
RE: Teamserver issues after migration
Thanks Gerard,
It was, as you suggested, related to the change of Bizflow IDs when we copied data from Test to Dev. Team server did not move but it saw the new IDs with the same name (I guess) as duplicates. We were able to reestablish our old IDs by some machinations on Bizflow tables and we're back in business.
Find all posts by this user
Quote this message in a reply
24-Jan-2017, 11:30 AM
Post: #4
RE: Teamserver issues after migration
Hi Sherman,

I'm glad you've got everything working again, and thanks for letting us know what you needed to change.

Regards,
Gerard
Find all posts by this user
Quote this message in a reply
Post Reply 


Possibly Related Threads...
Thread: Author Replies: Views: Last Post
  Team Server Issues kidder 10 1,457 19-Sep-2016 11:19 AM
Last Post: Craig

Forum Jump:


User(s) browsing this thread: 1 Guest(s)