Here is my web.config file
<?xml version="1.0" encoding="utf-8" ?>
<configuratio n>
<system.web>
<!-- DYNAMIC DEBUG COMPILATION
Set compilation debug="true" to enable ASPX debugging.
Otherwise, setting this value to
false will improve runtime performance of this application.
Set compilation debug="true" to insert debugging symbols
(.pdb information)
into the compiled page. Because this creates a larger file
that executes
more slowly, you should set this value to true only when
debugging and to
false at all other times. For more information, refer to the
documentation about
debugging ASP.NET files.
-->
<compilation defaultLanguage ="c#" debug="true">
<assemblies>
<add assembly="Cryst alDecisions.Cry stalReports.Eng ine,
Version=9.1.500 0.0, Culture=neutral , PublicKeyToken= 692fbea5521e130 4"
/>
<add assembly="Cryst alDecisions.Rep ortSource, Version=9.1.500 0.0,
Culture=neutral , PublicKeyToken= 692fbea5521e130 4" />
<add assembly="Cryst alDecisions.Sha red, Version=9.1.500 0.0,
Culture=neutral , PublicKeyToken= 692fbea5521e130 4" />
<add assembly="Cryst alDecisions.Web , Version=9.1.500 0.0,
Culture=neutral , PublicKeyToken= 692fbea5521e130 4" />
</assemblies>
</compilation>
<!-- CUSTOM ERROR MESSAGES
Set customErrors mode="On" or "RemoteOnly " to enable custom
error messages, "Off" to disable.
Add <errortags for each of the errors you want to handle.
"On" Always display custom (friendly) messages.
"Off" Always display detailed ASP.NET error information.
"RemoteOnly " Display custom (friendly) messages only to users
not running
on the local Web server. This setting is recommended for
security purposes, so
that you do not display application detail information to
remote clients.
-->
<customErrors mode="RemoteOnl y" />
<!-- AUTHENTICATION
This section sets the authentication policies of the
application. Possible modes are "Windows",
"Forms", "Passport" and "None"
"None" No authentication is performed.
"Windows" IIS performs authentication (Basic, Digest, or
Integrated Windows) according to
its settings for the applicat<A
HREF="http://localhost/Santosh/DesMng/SelectDatabase. aspx">http://localhost/Santosh/DesMng/SelectDatabase. aspx</A>ion.
Anonymous access must be disabled in IIS.
"Forms" You provide a custom form (Web page) for users to
enter their credentials, and then
you authenticate them in your application. A user credential
token is stored in a cookie.
"Passport" Authentication is performed via a centralized
authentication service provided
by Microsoft that offers a single logon and core profile
services for member sites.
-->
<authenticati on mode="Windows" />
<!-- AUTHORIZATION
This section sets the authorization policies of the
application. You can allow or deny access
to application resources by user or role. Wildcards: "*" mean
everyone, "?" means anonymous
(unauthenticate d) users.
-->
<authorizatio n>
<allow users="*" /<!-- Allow all users -->
<!-- <allow users="[comma separated list of users]"
roles="[comma separated list of roles]"/>
<deny users="[comma separated list of users]"
roles="[comma separated list of roles]"/>
-->
</authorization>
<!-- APPLICATION-LEVEL TRACE LOGGING
Application-level tracing enables trace log output for every
page within an application.
Set trace enabled="true" to enable application trace logging.
If pageOutput="tru e", the
trace information will be displayed at the bottom of each
page. Otherwise, you can view the
application trace log by browsing the "trace.axd" page from
your web application
root.
-->
<trace enabled="false" requestLimit="1 0" pageOutput="fal se"
traceMode="Sort ByTime" localOnly="true " />
<!-- SESSION STATE SETTINGS
By default ASP.NET uses cookies to identify which requests
belong to a particular session.
If cookies are not available, a session can be tracked by
adding a session identifier to the URL.
To disable cookies, set sessionState cookieless="tru e".
-->
<sessionState mode="InProc"
stateConnection String="tcpip=1 92.168.0.224" sqlConnectionSt ring="data
source=127.0.0. 1;Trusted_Conne ction=Yes"
cookieless="fal se" timeout="20" />
<!-- GLOBALIZATION
This section sets the globalization settings of the
application.
-->
<globalizatio n requestEncoding ="utf-8" responseEncodin g="utf-8" />
<httpHandlers >
<!--
Please note, this is only for ASP.NET 1.0 and 1.1.
This line does not need to be included in ASP.NET 2.0
-->
<add verb="GET" path="FtbWebRes ource.axd"
type="FreeTextB oxControls.Asse mblyResourceHan dler, FreeTextBox" />
</httpHandlers>
<identity impersonate="tr ue">
</identity>
</system.web>
<appSettings>
<add key="CnnString" value="DSN=vrit ti; uid=sa; pwd=sa" />
</appSettings>
</configuration>
Regards
Santosh.
Nate wrote:
I would look at the documentation for Crystal Reports on how to configure for
an asp.net app (maybe a license key entry needs to go in the <appsettings>
section of the web.config)... Most 3rd party products are designed to work as
localhost even w/o purchasing (in order for trial development).
"Santosh" wrote:
Hii ,
i am developing an web application using asp.net with in it reporting
purpose i am using crystal reports. it is working on fine on local
server. but when i deploy it on web server it gives me an keycodedll
error. i am trying the things like building web set up adding merge
modules. passing registration key from .Net Help menu, About.Net. but
it still giving same error. can anyone tell me can it is sufficient to
pass registration key registration key from .Net Help menu, About.Net
for running crystal report over web server.
any help will greatly appreciated.
