Crystal Reports access denied error

Hello,
I've been stumped trying to resolve the following error when running Crystal Reports on a new server I'm setting up:

HTTP 500.100 - Internal Server Error - ASP error
Internet Information Services

------------------------

Technical Information (for support personnel)

Error Type:
Seagate Crystal Reports ActiveX Designer (0x80043AC6)
Access denied.
/OrbitRpt/Crystal/AlwaysRequiredSteps.asp, line 57

I'm running a Win2K server (service pack 4) with Crystal Reports 8. I've tried setting the security to "Everyone - Full Control" on all folders but I'm still getting the "Access denied" error. Has anyone seen this before? Any info would be greatly appreciated. Thanks!The following changes fixed my problem:
To properly set up your System Environment Variables:

1. Create the directory "C:\Temp" if it is not already created.
2. Right-click on "My Computer" on the server machine, and choose "Properties".
3. Go to the "Environment" tab.
4. Under "User Variables", select "TEMP", and then click "Remove". Repeat for the variable "TMP".
5. Select any variable under "System Variables".
6. Change the value for "Variable" to "TEMP" (no quotes).
7. Change the value for "Value" to "C:\Temp" (no quotes).
8. Click "Set".
9. Change the value for "Variable" to "TMP" (no quotes).
10. Change the value for "Value" to "C:\Temp" (no quotes).
11. Click "Set".
12. Click "OK".

Be sure to give "Read" and "Delete" access to this TEMP folder so that the Crystal Reports web components can read and write to this directory.

Crystal Report

I would like to automate the printing of some Crystal reports that I run daily and was thinking about setting up a scheduled task to automate the printing. Any suggestions?

Cheryl

I think you are in the wrong forum. This is for microsoft reporting services (similar to Crystal Enterprise).

Cross DB ownership chaining

Hello,
I am having trouble setting up cross db ownership chaining. Did I omit
anything?
1. Using SQL Server 2000 SP3a.
2. Login as 'sa'.
3. Create new database A1.
4. Create new database A2.
5. Create TableA in database A2.
6. Create view vTableA in database A1 as select * from A2.dbo.TableA
7. Add UserA to database A1.
8. Grant select permission on vTableA to UserA.
9. Enable cross database ownerchip chaining option in database A1 and A2.
10. All objects are owned by dbo and both databases are owned by 'sa'.
11. Log in as UserA and run Select * from vTableA in database A1, get error
"Server user 'UserA' is not a valid user in database 'A2'.".
Unless I'm missing something, I was expecting the last step to work. Any
help greatly appreciated.
PaulUserA needs a security context in database A2, although no object
permissions need be granted. You can either add the user to database A2 or
enable the guest user in database A2.
Hope this helps.
Dan Guzman
SQL Server MVP
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:43D9406C-1C28-4A86-BF39-9A2D7E1B2CFB@.microsoft.com...
> Hello,
> I am having trouble setting up cross db ownership chaining. Did I omit
> anything?
> 1. Using SQL Server 2000 SP3a.
> 2. Login as 'sa'.
> 3. Create new database A1.
> 4. Create new database A2.
> 5. Create TableA in database A2.
> 6. Create view vTableA in database A1 as select * from A2.dbo.TableA
> 7. Add UserA to database A1.
> 8. Grant select permission on vTableA to UserA.
> 9. Enable cross database ownerchip chaining option in database A1 and A2.
> 10. All objects are owned by dbo and both databases are owned by 'sa'.
> 11. Log in as UserA and run Select * from vTableA in database A1, get
> error
> "Server user 'UserA' is not a valid user in database 'A2'.".
> Unless I'm missing something, I was expecting the last step to work. Any
> help greatly appreciated.
> Paul|||(thump on head) Thanks Dan, that did it.
"Dan Guzman" wrote:

> UserA needs a security context in database A2, although no object
> permissions need be granted. You can either add the user to database A2 o
r
> enable the guest user in database A2.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:43D9406C-1C28-4A86-BF39-9A2D7E1B2CFB@.microsoft.com...
>
>

Cross database transactions.

Are Cross database transactions enabled by default? Not cross-server,
just cross database. If not what setting should I be looking at?Hi Frank
There is nothing special you need to do to enable cross database
transactions. Just make sure you have the necessary rights to the objects in
both databases.
--
HTH
Kalen Delaney, SQL Server MVP
www.InsideSQLServer.com
http://sqlblog.com
"Frank Rizzo" <none@.none.com> wrote in message
news:%238lZ7g24HHA.4964@.TK2MSFTNGP06.phx.gbl...
> Are Cross database transactions enabled by default? Not cross-server,
> just cross database. If not what setting should I be looking at?

Cross apply requires 9.0 compatibility

If SQL 2000 must access a 2005 database continually, does it require setting
the compatibility to 8.0? What are the consequences of setting the 2005
database to 9.0 under these circumstances? (Trying to get cross apply to
work with 8.0 compatibility set on SQL 2005).
Regards,
Jamie
Got it... fire off from master which will use version 9.0 irregardless of
server setting.
Regards,
Jamie
"thejamie" wrote:

> If SQL 2000 must access a 2005 database continually, does it require setting
> the compatibility to 8.0? What are the consequences of setting the 2005
> database to 9.0 under these circumstances? (Trying to get cross apply to
> work with 8.0 compatibility set on SQL 2005).
> --
> Regards,
> Jamie
|||That's a useful tidbit there!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:845339A7-B70C-4BEB-B556-2C3F061318D1@.microsoft.com...[vbcol=seagreen]
> Got it... fire off from master which will use version 9.0 irregardless of
> server setting.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:

Cross apply requires 9.0 compatibility

If SQL 2000 must access a 2005 database continually, does it require setting
the compatibility to 8.0? What are the consequences of setting the 2005
database to 9.0 under these circumstances? (Trying to get cross apply to
work with 8.0 compatibility set on SQL 2005).
--
Regards,
JamieGot it... fire off from master which will use version 9.0 irregardless of
server setting.
--
Regards,
Jamie
"thejamie" wrote:

> If SQL 2000 must access a 2005 database continually, does it require setti
ng
> the compatibility to 8.0? What are the consequences of setting the 2005
> database to 9.0 under these circumstances? (Trying to get cross apply to
> work with 8.0 compatibility set on SQL 2005).
> --
> Regards,
> Jamie|||That's a useful tidbit there!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:845339A7-B70C-4BEB-B556-2C3F061318D1@.microsoft.com...[vbcol=seagreen]
> Got it... fire off from master which will use version 9.0 irregardless of
> server setting.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:
>

Cross apply requires 9.0 compatibility

If SQL 2000 must access a 2005 database continually, does it require setting
the compatibility to 8.0? What are the consequences of setting the 2005
database to 9.0 under these circumstances? (Trying to get cross apply to
work with 8.0 compatibility set on SQL 2005).
--
Regards,
JamieGot it... fire off from master which will use version 9.0 irregardless of
server setting.
--
Regards,
Jamie
"thejamie" wrote:
> If SQL 2000 must access a 2005 database continually, does it require setting
> the compatibility to 8.0? What are the consequences of setting the 2005
> database to 9.0 under these circumstances? (Trying to get cross apply to
> work with 8.0 compatibility set on SQL 2005).
> --
> Regards,
> Jamie|||That's a useful tidbit there!
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"thejamie" <thejamie@.discussions.microsoft.com> wrote in message
news:845339A7-B70C-4BEB-B556-2C3F061318D1@.microsoft.com...
> Got it... fire off from master which will use version 9.0 irregardless of
> server setting.
> --
> Regards,
> Jamie
>
> "thejamie" wrote:
>> If SQL 2000 must access a 2005 database continually, does it require
>> setting
>> the compatibility to 8.0? What are the consequences of setting the 2005
>> database to 9.0 under these circumstances? (Trying to get cross apply to
>> work with 8.0 compatibility set on SQL 2005).
>> --
>> Regards,
>> Jamie