Steve,
If RedDotUser was set up as a domain account, the target drive needs
to be accessible to that domain account.
Anyway, if all checks fail, it could be just the CMS interfcace is
"faking" the check -- it is not actually "checking", instead, it is
just alerting out the "Error, Path not found" message without actually
checking.
UNC checking is just a simple <admin> action in terms of RQL. You can
run a simle RQL after login in and use the <iodata> listed as follows:
xmlData = "<IODATA loginguid=" & Chr(34) & guid_login & Chr(34) & ">" &
_
"<ADMINISTRATION loginguid=" & Chr(34) & guid_login &
Chr(34) & "
action=" & Chr(34) & "checkuncpath" & Chr(34) & " path=" & Chr(34) &
sUNCPath & Chr(34) & " user="""" password="""" /></IODATA>"
Where guid_login can be obtained from session (Session("LoginGuid"))
or manually obtained when you do <administration action="login" />
sUNCPath is the string representing the path. Remember to actually put
in the RedDotUser credential in the user/pass fields. If the path
checks out, there will be an attribute in the return xml tag:
success="1".
If this fails, you know there is permission issue. If this goes
through, you know that the pubblishing targets are good, its just CMS
user interface is not behaving.
If it is latter case, check to make sure in RDServer.ini the
"RedDot-User Domain=" has the correct domain appended if it is a
domain account.
And you make want to do "iisreset" or re-start the WWW service from
service panel so the UNC checking in CMS can start anew.
Henry Lu
On Mon, Sep 8, 2008 at 9:29 AM, Joshua <[EMAIL PROTECTED]> wrote:
>
> On Sep 8, 9:08 am, Steve <[EMAIL PROTECTED]> wrote:
>
>> Has anyone ever receive the following error: "Error: 76, Path not
>> found" when checking the path under Publishing Target?
>
> Yes, we've encountered this -- in every instance I can think of either
> the RedDot was failing to authenticate on the remote machine, or the
> RedDot user was authenticating, but being denied access to the share.
> Normally the line of inquiry goes like this: Is there a user account
> on your target server with the same name and password as the local
> RedDot user account on your RedDot server? Does the share being
> accessed in the publishing path still exist on the target server? Does
> the RedDot user have access to the share? Does the RedDot user on the
> target publishing machine have rights to log on locally and/or access
> the machine from the network? But it sounds like you've already
> checked these things.
>
> If you have access, you might want to check the Security event logs of
> both the CMS and target server to see if anything shows up. If it
> isn't already, enable login attempt and object access failure auditing
> on both servers.
>
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"RedDot CMS Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/RedDot-CMS-Users?hl=en
-~----------~----~----~----~------~----~------~--~---
