Hi Jackson
I am having the exact same problem. Did you find a solution? Should I find
one I will post it here.
Tina - MSFTE
> I'm having a problem connecting to an access database from
> http://localhost/reports. I can connect from the computer I developed the
[quoted text clipped - 15 lines]
>
> Jackson
Jackson - 31 Aug 2005 16:22 GMT
It took a while but I finally got a work around.
I'm currently taking daily snapshots of the access reports. So now I don't
even need to create odbc connections on other user computers.
> Hi Jackson
>
[quoted text clipped - 24 lines]
>>
>> Jackson
Jackson and Tina
I am having the same problem and have posted everywhere trying to find a
fix. This supposedly works. I have turned it over to the Network Mgr and he
is reviewing it. Hopefully, it will solve the problem. If it works, please
let me know or, if you find another solution I wuld really appreciate hearing
about it.
Roy
1. Kerberos is enabled
2. The servers are trusted for delegation
3. The SPN's are configured
"http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_sec
urity_2gmm.asp"
4. If you have several domain controllers wait for replication to complete.
If you don't wait you will pull your hair out because nothing you try will
works and all of sudden a few hours latter it starts working and you can't
figure out why.
5. Make sure all users have the option 'Enable Integrated Windows
Authentication' enabled in internet explorer, without it they will still get
the authentication error.
> I'm having a problem connecting to an access database from
> http://localhost/reports. I can connect from the computer I developed the
[quoted text clipped - 15 lines]
>
> Jackson
Tina (MSFTE) - 31 Aug 2005 19:04 GMT
Roy,
Your post put me on the right track. The IIS server we deployed to is not in
a domain, neither was any of the users. I did not even think of looking for
this scenario, I assumed we were on the domain.
1) I requested a user to be created on the domain.
2) I gave this user Data reader rights on all the SQL and AS servers that
forms part of my solution
3) In RS I used the full username and password to be saved securely in RS
4) Selected "Use as WIS credentials to make the connection"
5) Selected "Impersonate user after connection created"
It works like a charm. Due to the client's unique network configuration -
servers on the network, but not in the domain - this is the only way the
solution will work.
> Jackson and Tina
> I am having the same problem and have posted everywhere trying to find a
[quoted text clipped - 35 lines]
> >
> > Jackson
I ran into the same issue. I have modified security to report howeve
I noticed that it is using the users credentials who is accessing th
report to initiate Oracle connection. It looks like the use
requires elevated permissions on C:\Program Files\Oracle and possibl
other directories
Still investigating...
Rya
Tina (MSFTE) - 31 Aug 2005 21:43 GMT
If you creaye a secure use in RSthat user can have the elevated priviledges
and not your real life users - better from a security point of view - that is
why I selected the options I did. See if that works to Oracle as well.
Cioa
Tina
> I ran into the same issue. I have modified security to report however
> I noticed that it is using the users credentials who is accessing the
[quoted text clipped - 5 lines]
>
> Ryan