slxdeveloper.com Community Forums

The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!

Administration Forums - Database Administration
Forum to discuss SQL Server or Oracle database administration related to SalesLogix databases. View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to Database Administration | New Thread

View: Search:

Author

Thread: How to Synch TEFS after a remote user has been assigned a new Site Code

Tom
Posts: 58

How to Synch TEFS after a remote user has been assigned a new Site Code Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 13 Nov 07 10:59 AM

Does anyone know how to Synch TEFS after a remote user has been assigned a new Site Code. Somehow the remote user is using an old site code XCSF and the Admin shows their site code as 9EJD. As a result, there are a bunch of transaction files which wound up in the Rejected Folder in the Infiles. How can I process these TEFS?

[Reply][Quote]

David Henry
Posts: 207

Re: How to Synch TEFS after a remote user has been assigned a new Site Code Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 13 Nov 07 1:28 PM

Does the "old" site code belong to a retired user? If so, bring the user out of retired status as Active/Remote and then move the TEFs from Rejected to Infiles.

If the files still get rejected on the next sync cycle you could try this: Detach the user's remote database and try using the RESYNCHRONIZE DATABASE tool in the WGAdmin. Then cut and replace the user's database with a fresh one using the correct site code.

[Reply][Quote]

Tom
Posts: 58

Re: How to Synch TEFS after a remote user has been assigned a new Site Code Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 13 Nov 07 1:37 PM

Thanks, but here is how I went about it. The only difference is when you change the user's site code it puts the Key Base at '0', so then I had to change the Key Base to match that of the TEF files. '1' then the synch server applied the changes.

Description:

Possible Resolution:

Before beginning this process, verify both sitecodes are in the SiteOptions table.
1. Make a full and complete backup of the host database.
2. In the UserSecurity table, change the data in PrimarySite from the new sitecode to the old sitecode.
3. Check the SyncSequencing table entry where the old sitecode is in the SourceSite field.
4. Note the data in the ApplyIndex field.
5. Check the name of the oldest tef for the old sitecode in the Rejected folder. It should be the next number after the one noted in SyncSequencing.
6. Move all tefs for the old sitecode from Rejected in Infiles. If there are multiple sync servers, ensure the tefs are placed in the correct Infiles folder.
7. Stop the Sync Service and manually cycle the Sync Server.
8. Once the tefs have all been applied, create a new database with a new sitecode.
9. Delete any tefs with the new sitecode from the appropriate Archives and Outfiles folders.

Update USERSECURITY set PRIMARYSITE = '' where USERID = '' and PRIMARYSITE = ''
Update SITEOPTIONS set PRIMARYSERVER = '' where SITECODE = ''
Update SITEOPTIONS set PRIMARYSERVER = '' where SITECODE = ''

Backup DB first, and cut new remote with new site code last.

[Reply][Quote]

Page 1 of 1

You can subscribe to receive a daily forum digest in your user profile. View the site code of conduct for posting guidelines.

Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!

slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation. This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 11/25/2024 4:41:48 PM