After having upgraded to Reporter 5.4 from version 2.2, I'm attempting to set the network archive location. For our existing Windows server archive location, I've tried \\servername\sharename ,
\\ip address\sharename and X: drive letter ( that's novell mapped at login) without any luck. The authentication field parameters I've tried are DOMAIN\username with the appropriate password in the field below it as well as simply username with the appropriate password in the field below it. Nothing seems to work. Reporter still flashes red at the bottom left corner of the Reporter 5.4 GUI complaining about the archive specifics. The parameters I've tried are indeed valid as I have other Reporter version 2.2 pcs running with just the drive letter ( X: ) as the archive location for audio.
Any suggestions other than wiping the pc and installing windows and FTR reporter from the ground up?
Thanks,
Bruce
Page 1 of 1
5.4 Reporter Archive Settings
#2
Posted 30 July 2010 - 01:34 AM
The easiest way to configure Replicator to archive to a mapped drive is to run the S2A Utility
please read the KB article here
http://community.for...-network-drive/
Currently this is only designed for 32 bit windows we are working on a 64 bit version
We have noticed with our testing of Novell archiving issues that they are generally caused by the PC trying to have multiple connections to a server using different credentials, Novell will usually drop the first connection
e.g. One mapped drive logged on the logged on user
Replicator archiving configured to use administrator
in this case from our testing it appears that as Replicator connects first due to it being a service, when the mapped drive connects as a different user it will drop the replicators connection
or
One mapped drive logged on the logged on user
another mapped drive logged on as administrator
in this case from our testing, when the second mapped drive connects it will drop the first mapped drives connection
please read the KB article here
http://community.for...-network-drive/
Currently this is only designed for 32 bit windows we are working on a 64 bit version
We have noticed with our testing of Novell archiving issues that they are generally caused by the PC trying to have multiple connections to a server using different credentials, Novell will usually drop the first connection
e.g. One mapped drive logged on the logged on user
Replicator archiving configured to use administrator
in this case from our testing it appears that as Replicator connects first due to it being a service, when the mapped drive connects as a different user it will drop the replicators connection
or
One mapped drive logged on the logged on user
another mapped drive logged on as administrator
in this case from our testing, when the second mapped drive connects it will drop the first mapped drives connection
Mark D'Arcy, Senior Systems Engineer
Support Dept, Perth
Support Dept, Perth
#3
Posted 02 August 2010 - 08:23 PM
Mark D, on 30 July 2010 - 01:34 AM, said:
The easiest way to configure Replicator to archive to a mapped drive is to run the S2A Utility
please read the KB article here
http://community.for...-network-drive/
Currently this is only designed for 32 bit windows we are working on a 64 bit version
We have noticed with our testing of Novell archiving issues that they are generally caused by the PC trying to have multiple connections to a server using different credentials, Novell will usually drop the first connection
e.g. One mapped drive logged on the logged on user
Replicator archiving configured to use administrator
in this case from our testing it appears that as Replicator connects first due to it being a service, when the mapped drive connects as a different user it will drop the replicators connection
or
One mapped drive logged on the logged on user
another mapped drive logged on as administrator
in this case from our testing, when the second mapped drive connects it will drop the first mapped drives connection
please read the KB article here
http://community.for...-network-drive/
Currently this is only designed for 32 bit windows we are working on a 64 bit version
We have noticed with our testing of Novell archiving issues that they are generally caused by the PC trying to have multiple connections to a server using different credentials, Novell will usually drop the first connection
e.g. One mapped drive logged on the logged on user
Replicator archiving configured to use administrator
in this case from our testing it appears that as Replicator connects first due to it being a service, when the mapped drive connects as a different user it will drop the replicators connection
or
One mapped drive logged on the logged on user
another mapped drive logged on as administrator
in this case from our testing, when the second mapped drive connects it will drop the first mapped drives connection
#4
Posted 02 August 2010 - 08:41 PM
Thanks Mark, That did the trick for a given user who's logged on with a mapped drive as the archive location. Is there any way to specify the Log Notes folder, other than accepting the default of \LogSheets ?
On another note, I REALLY need an answer to another problem we're having. I'll submit another post named Gold Log Notes 5.4 Upgrade from 2.2
On another note, I REALLY need an answer to another problem we're having. I'll submit another post named Gold Log Notes 5.4 Upgrade from 2.2
#5
Posted 03 August 2010 - 01:21 AM
It is not recomended to change the archive path for the log sheet folder, our software expects the log sheet folder to be in a sub folder of the recordings called logsheets.
Mark D'Arcy, Senior Systems Engineer
Support Dept, Perth
Support Dept, Perth
Share this topic:
Page 1 of 1

Help











