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!
|
|
V6.2.3 -> v7 "Logging Server Does not have access to the specified path"
Posted: 12 Oct 06 7:22 PM
|
fiogf49gjkf0d Hi all,
Copied my live database over to a test server that is not on our domain. Went through the steps in the v6 document of "using a copy of your production database in a test environment" (Doc ID 03010106)
However, once upgraded to v7, I get "Logging Server does not have access to the specified path" in the client and architect.
I've editied:
BRANCHOPTIONS.ATTACHMENTPATH
BRANCHOPTIONS.SALESLIBRARYPATH
SYNCSERVER.SERVERPATH
There were no entries to delete in SYNCTRANSFER and SYNCSERVICEFILE. We actually don't do sync'ing anyways.
Anyone know what else do I need to alter to get the test database up and running? |
|
|
|
Re: V6.2.3 -> v7 "Logging Server Does not have access to the specified path"
Posted: 13 Oct 06 3:19 PM
|
fiogf49gjkf0d Originally posted by Mike Mahoney
Hi all,
Copied my live database over to a test server that is not on our domain. .......
Anyone know what else do I need to alter to get the test database up and running? |
|
You answered it.. permissions.. The test server is not in your domain.... so you need to authenticate.
--
rjl |
|
|
| |
|
Re: V6.2.3 -> v7 "Logging Server Does not have access to the specified path"
Posted: 13 Oct 06 6:50 PM
|
fiogf49gjkf0d Have you updated the connection manager info? It updates a field in the database to point to the different server if the name of the computer changed. You can always verify it by running this query:
select pingserver from systeminfo
Are you running Administrator at all? It typically never sees the logging error message and generally when you see it, it's a configuration/user error type of thing.
Are you operating in a VM? If so is your network connected? VMWare complains 3 times per every boot cycle (including shutdown) whenever I leave the connection enabled but the cable is unplugged. The problem with disabling the connection is somehow it turns off the MS Networking crap that tells SalesLogix it can use \\COMPUTERNAME\SHARE. I've been too lazy to research getting around the problem but it gives me the same exact error message until I turn networking back on. |
|
|
|
Re: V6.2.3 -> v7 "Logging Server Does not have access to the specified path"
Posted: 15 Oct 06 4:22 PM
|
fiogf49gjkf0d Hi Jeremy,
What I did do was start over. I joined the test server to the domain, and upgraded the database. I then installed the server and workstation components using a domain admin as the user account for the services. That fixed that problem. Onto the next one..
Now, opening the client gets me the error "EoleException - Invalid object name 'FEATURERSECURITY'
Sounds like my upgrade did not take correctly. Thoughts, anyone?
-M1 |
|
|
|
Re: V6.2.3 -> v7 "Logging Server Does not have access to the specified path"
Posted: 15 Oct 06 6:22 PM
|
fiogf49gjkf0d Update! Got rid of the EOleException error by re-running the upgrade bundle.
So the thing I take away from this is...
1. Always use a domain services account to run all the SLX services.
2. It doesn't hurt to "upgrade" the upgrade bundle to be sure everything took.
3. There still isn't any way to disable synchronization. In our case, we have a license but don't use it.
-M1 |
|
|
|
Re: V6.2.3 -> v7 "Logging Server Does not have access to the specified path"
Posted: 15 Oct 06 8:44 PM
|
fiogf49gjkf0d Originally posted by Mike Mahoney
3. There still isn't any way to disable synchronization. In our case, we have a license but don't use it. |
|
When you say there is no way to disable synchronization what exactly are you expecting?
If the SyncServer license is not installed then I would expect no workgroup logs to be created. |
|
|
|
Re: V6.2.3 -> v7 "Logging Server Does not have access to the specified path"
Posted: 16 Oct 06 3:02 AM
|
fiogf49gjkf0d re: removing SyncServer license and defintion.
I don't know if this TSQL will fit in my reply msg - but here goes.... USE AT OWN RISK
-- script: makeSafeDevTestDB.sql
-- Author: Todd Hardin, Customer Systems Inc.
-- Revision: 1.1
-- Release: For public release, *USE AT OWN RISK*
--
-- IMPORTANT NOTE: Assumes you are logged in as SA user
--
use
go
-- Assuming this database has just been Restored/Attached
-- Can't hurt to run this.
print 'Perform fixup on sysdba login to user mapping for this DB'
exec sp_change_users_login 'Update_One', 'sysdba', 'sysdba'
print ' '
-- declare variables
declare @dbname varchar(32)
declare @newHostSiteCode char(4)
declare @oldHostSiteCode char(4)
declare @LibraryUNC varchar(128)
declare @AttachmentsUNC varchar(128)
-- initialize implementation specific variables
-- NOTE: edit these values as desired for your implementation
-- #####################################################################
select @newHostSiteCode = 'AAAA'
select @LibraryUNC = '\\YourServer\DevShares\Library'
select @AttachmentsUNC = '\\YourServer\DevShares\Attachments'
-- Retrieve the current site code for the Main host system
select @oldHostSiteCode = sitecode from sysdba.systeminfo where systeminfoid = 'PRIMARY'
-- #####################################################################
-- Section 1: Remove all SyncServer and RemoteOffice Definitions
print 'Section 1: Remove all SyncServer and RemoteOffice Definitions'
print '#############################################################'
print ' '
-- delete siteoptions records that are tied to syncservers
print 'deleting siteoptions records that are tied to syncservers'
delete from sysdba.siteoptions where sitecode in (select sitecode from sysdba.syncserver)
-- delete license records that represent any syncserver
print 'deleting license record(s) that represent any syncserver(s)'
delete from sysdba.licenses where userid in (select sitecode from sysdba.SyncServer)
-- update siteoptions table for records which represent users
print 'updating hostserver reference in siteoptions table for all records which represent system users'
update sysdba.siteoptions set hostserver = 'NOSYNCSERVER' where sitecode in (select primarysite from sysdba.usersecurity)
-- Ideally we would have cleand up the SiteOptions blob to remove mapping of User to SyncTransfer profile.
-- Had considered setting blob = NULL
-- Decided to leave blob alone as blob appears to also be used for LAN users.
-- cleanup branchoptions table
-- delete any remote offices defined
print 'deleting all remote office definitions'
delete from sysdba.branchoptions where sitecode not in (select primaryserver from sysdba.systeminfo where systeminfoid = 'PRIMARY')
-- update the record representing the main host office
print 'updating branchoptions table for record representing main host office'
update sysdba.branchoptions set sitecode = 'NOSYNCSERVER', attachmentpath = @AttachmentsUNC, saleslibrarypath = @LibraryUNC
-- delete all syncserver definitions
print 'deleting all syncserver definitions from syncserver table'
delete from sysdba.syncserver
-- delete the UNC to the sync service job definition file
print 'deleting syncservicefile (sync job file) record'
delete from sysdba.syncservicefile
-- delete any SyncTransfer profile definitions
print 'deleting all sync transfer profile definitions from synctransfer table'
delete from sysdba.synctransfer
-- change all Remote (Mobile) users to Network users
print 'changing all remote users to be network users in usersecurity table'
update sysdba.usersecurity set type = 'N' where type = 'M'
-- delete all prior usersubscription information
print 'deleting all usersubscription information since users are no longer remotes'
delete from sysdba.usersubscription
-- cleanup syncserver work tables
print 'deleting sync work table - synsequencing'
delete from sysdba.syncsequencing
print 'deleting sync work table - syncjobhistory'
delete from sysdba.syncjobhistory
print 'deleting sync work table - syncfiletracking'
delete from sysdba.syncfiletracking
-- special clean-up for discontinue IQ Reporting tool
print 'deleting legacy IQ Objects schema record from systeminfo table'
delete from sysdba.systeminfo where systeminfoid = 'IQKBASE'
-- clean up the systeminfo table
print 'updates to system info table to cleanup record for main host office'
-- uncomment if SLX v6.0.1
--update sysdba.systeminfo set primaryserver = 'NOSYNCSERVER', pingport = NULL, pingserver = NULL, RWPass = NULL
-- This version for SLXv6.1; NULLs out new column "ROPASS"
update sysdba.systeminfo set primaryserver = 'NOSYNCSERVER', pingport = NULL, pingserver = NULL, RWPass = NULL, ROPass = NULL
-- ##################################################################
-- Section 2: Remove all SLX Web configuration information
print 'Section 2: Remove all SLX Web configuration information'
print '#############################################################'
print ' '
-- delete siteoptions records the correspond to WebServer DLL Instances
print 'deleting siteoptions records the correspond to WebServer DLL Instances'
delete from sysdba.siteoptions where sitecode in (select sitecode from sysdba.slxwebserver)
-- delete web server defintion(s)
print 'deleting web server defintion(s) from slxwebdata table'
delete from sysdba.slxwebdata
-- delete web server DLL instance definition(s)
print 'deleting web server DLL instance definition(s) from slxwebserver table'
delete from sysdba.slxwebserver
-- ##################################################################
-- Section 3: Change the SiteCode of the main/host system
print 'Section 3: Change the SiteCode of the main/host system'
print '#############################################################'
print ' '
print 'Updating main host site code from: ' + @oldHostSiteCode + ' to: ' + @newHostSiteCode
-- update siteoptions table to reflect the newHostSiteCode
print 'Updating sitecode in siteoptions table for record representing main host office'
update sysdba.siteoptions set sitecode = @newHostSiteCode where sitecode = @oldHostSiteCode
-- update systeminfo table to reflect the newHostSiteCode
print 'updating systeminfo table to reflect the newHostSiteCode'
update sysdba.systeminfo set sitecode = @newHostSiteCode where sitecode = @oldHostSiteCode
-- update sitekeys to newHostSiteCode as well as resetting key generator base values
-- easy way - SLX will rebuild this table when needed.
print 'deleting all records from sitekeys table. SLX will rebuild on demand using new sitecode'
delete from sysdba.sitekeys
-- alternative technique
-- delete from sysdba.sitekeys where sitecode <> @oldHostSiteCode
-- update sysdba.sitekeys set sitecode = @newHostSiteCode, keyvalue = 'A000000'
-- ###################################################################
-- Section 4: Change the sitecode for each USER
-- This proceedure uses a sequentially assigned decimal number
-- for each USER sitecode.
-- U001 - U999
-- Ideally we should check for collisions on the rare change
-- that a SITECODE of the form U### already exists in the database.
--
-- An alternative would be to use randomly assigned base36 values
-- just as SLX does.
--
print 'Section 4: Change the sitecode for each USER'
print '#############################################################'
print ' '
declare userlist cursor for select primarysite from sysdba.usersecurity
declare @oldUserSiteCode char(4)
declare @newUserSiteCode char(4)
declare @UserCounter int
-- init counter
select @UserCounter = 0
open userlist
fetch next from userlist into @oldUserSiteCode
while @@fetch_status = 0
begin
select @UserCounter = @UserCounter + 1
select @newUserSiteCode = 'U' + right ('000' + CAST(@UserCounter as varchar), 3)
print 'Updating user sitecode from: ' + @oldUserSiteCode + ' to: ' + @newUserSiteCode
update sysdba.siteoptions set sitecode = @newUserSiteCode where sitecode = @oldUserSiteCode
update sysdba.usersecurity set primarysite = @newUserSiteCode where primarysite = @oldUserSiteCode
fetch next from userlist into @oldUserSiteCode
end
close userlist
deallocate userlist
-- ###################################################################
-- Section 5: Manual Tasks
print 'Section 5: Manual Tasks'
print '#############################################################'
print ' '
print 'Must do:'
print 'Edit/Recreate the Data Connection definition for this database'
print 'This is necessary to populate the systeminfo table columns'
print 'pingport, pingserver, and RWPass'
print ' '
print ' '
print 'End of script'
-- Optional: SyncServer, RemoteOffices, etc.
-- If you need a sync server or remote offices for your Dev/Test environment, then
-- install licenses and configure to use your Dev/Test SyncServer, Test FTp server, etc.
-- Optional: SLX WebServer
-- If you need to use the SLX Web features, use WebManager to defined new WebProfile(s) and WebServer(s)
-- configured to use your Dev/Test servers.
|
|
|
|
Re: V6.2.3 -> v7 "Logging Server Does not have access to the specified path"
Posted: 16 Oct 06 4:49 AM
|
fiogf49gjkf0d Hi,
Just go to administrator and go to systems tab and select syncservers
right click on profiles and edit , just if you don't want to sync then delete whatever written in shared path for logging else check this path is accessible or not.
thats it it will work definetely.
thanks |
|
|
|
Re: V6.2.3 -> v7 "Logging Server Does not have access to the specified path"
Posted: 16 Oct 06 10:27 AM
|
fiogf49gjkf0d Wow. Thanks to everyone for their assistance.
I'm going to try "mahaveer's" solution for the time being. Todd, your script is a "keeper" for later use, particularly if I ever get let go here and decide to become a BP again. I'm also going to test deleting the sync server license and see what ramifications that has on things.
Thanks again everyone. |
|
|
|
Re: V6.2.3 -> v7 "Logging Server Does not have access to the specified path"
Posted: 16 Oct 06 12:40 PM
|
fiogf49gjkf0d When you remove the existing paths, all it does is default to C:\Documents and Settings\All Users\Application Data\SalesLogix\Sync. The sync server still creates the WG Logs, it just stores them locally.
The best option if you're not using the sync server is to remove the license altogether. It prevents the TEFs from being created completely, as they are a waste of CPU cycles in a testing environment. |
|
|
| |
|