Access Database

When i set up an odbc connection to a access database on a network path. I
get an error saying the path is invalid. I am running SP2 . I can use the
same odbc datasource to connect using excel on the report server but not
using any reports.When you are running the report in production remember the path is relative
to the report server, not your workstation. perhaps that is the problem
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
"Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
news:8F43DC51-A2AF-46CE-962A-995CDD504BF8@.microsoft.com...
> When i set up an odbc connection to a access database on a network path. I
> get an error saying the path is invalid. I am running SP2 . I can use the
> same odbc datasource to connect using excel on the report server but not
> using any reports.|||i use the unc path to the shared folder on the network. It works fine from
the designer.
"Wayne Snyder" wrote:
> When you are running the report in production remember the path is relative
> to the report server, not your workstation. perhaps that is the problem
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> "Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
> news:8F43DC51-A2AF-46CE-962A-995CDD504BF8@.microsoft.com...
> > When i set up an odbc connection to a access database on a network path. I
> > get an error saying the path is invalid. I am running SP2 . I can use the
> > same odbc datasource to connect using excel on the report server but not
> > using any reports.
>
>|||Yes, but does the account the report is running under have rights to that
unc path?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
news:1FD8B93F-0179-4892-A787-11E3C904CB1A@.microsoft.com...
>i use the unc path to the shared folder on the network. It works fine from
> the designer.
> "Wayne Snyder" wrote:
>> When you are running the report in production remember the path is
>> relative
>> to the report server, not your workstation. perhaps that is the problem
>> --
>> Wayne Snyder, MCDBA, SQL Server MVP
>> Mariner, Charlotte, NC
>> www.mariner-usa.com
>> (Please respond only to the newsgroups.)
>> I support the Professional Association of SQL Server (PASS) and it's
>> community of SQL Server professionals.
>> www.sqlpass.org
>> "Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
>> news:8F43DC51-A2AF-46CE-962A-995CDD504BF8@.microsoft.com...
>> > When i set up an odbc connection to a access database on a network
>> > path. I
>> > get an error saying the path is invalid. I am running SP2 . I can use
>> > the
>> > same odbc datasource to connect using excel on the report server but
>> > not
>> > using any reports.
>>|||I have a similar problem, which is almost certainly a permissions problem in
the target shared directory. When you say "Account the report is running
under" are you talking about stored credentials in the RDS (which do not seem
to work) or a SYSTEM account that RS is using to try to access this shared
dir. I have had no luck whatsoever so any assistance tyou could render would
be most appreciated.
Thanks
Mark
"Bruce L-C [MVP]" wrote:
> Yes, but does the account the report is running under have rights to that
> unc path?
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
> news:1FD8B93F-0179-4892-A787-11E3C904CB1A@.microsoft.com...
> >i use the unc path to the shared folder on the network. It works fine from
> > the designer.
> >
> > "Wayne Snyder" wrote:
> >
> >> When you are running the report in production remember the path is
> >> relative
> >> to the report server, not your workstation. perhaps that is the problem
> >>
> >> --
> >> Wayne Snyder, MCDBA, SQL Server MVP
> >> Mariner, Charlotte, NC
> >> www.mariner-usa.com
> >> (Please respond only to the newsgroups.)
> >>
> >> I support the Professional Association of SQL Server (PASS) and it's
> >> community of SQL Server professionals.
> >> www.sqlpass.org
> >>
> >> "Ganesh" <Ganesh@.discussions.microsoft.com> wrote in message
> >> news:8F43DC51-A2AF-46CE-962A-995CDD504BF8@.microsoft.com...
> >> > When i set up an odbc connection to a access database on a network
> >> > path. I
> >> > get an error saying the path is invalid. I am running SP2 . I can use
> >> > the
> >> > same odbc datasource to connect using excel on the report server but
> >> > not
> >> > using any reports.
> >>
> >>
> >>
>
>sql

Access Control List (structure) invalid - updating Virtual directory information

Hi,

I've just installed SQL server and then IIS and SQLCE tools.
I created a virtual directory and was trying to update the NTFS
permissions from SQLServer Connectivity management when i got the
following error - Access Control List (structure) invalid.

Has anyone come across this and if so, what did u do to fix it.

Thanks
LynThis seems to be an OS error, rather than something specific to MSSQL,
so you might get a better response in a Windows
admin/security/filesystem newsgroup. The error message is documented,
but the explanation is very minimal:

http://msdn.microsoft.com/library/d...w2kmsgs/393.asp

The replies to a previous (old) post about this error suggested using
CHKDSK to look for any NTFS corruption issues, so that might be worth a
go:

http://groups.google.ch/group/micro...43a9a59d?hl=en&

Simon|||Thanks

I'll give it a go

Simon Hayes wrote:
> This seems to be an OS error, rather than something specific to MSSQL,
> so you might get a better response in a Windows
> admin/security/filesystem newsgroup. The error message is documented,
> but the explanation is very minimal:
> http://msdn.microsoft.com/library/d...w2kmsgs/393.asp
> The replies to a previous (old) post about this error suggested using
> CHKDSK to look for any NTFS corruption issues, so that might be worth a
> go:
> http://groups.google.ch/group/micro...43a9a59d?hl=en&
> Simonsql