Printable View
I have tested the program and works on my local machine. Now, I wanted to test out the program on the production server so I uploaded my files (this is my first asp.net project).
Virtually nothing comes out when I access the login page (please see attachment). Did I miss something when I uploaded my files into the prod server?
Thanks.
It looks like the server controls aren't being rendered. If you "view source" on the page do you see your controls as
<asp:textbox id="txt1" runat="server" />
or just not present at all?
The only time this happened to me it was a fault with the hosting company and i'm not sure what they did to fix it sorry.
You probably need to check the server is properly running the .net framework and that all the permission's are set up correctly. Hopefully someone who knows more about the server side of things will answer you too.
Yes, it seems that the server is not running the .NET framework properly. Although V1.1 is installed, I needed to run the aspnet_regiis.exe -i (on the server).
Now, when access the page, I get an "Server Error in '/' Application" on a remote machine. Going to the server itself, it tells me that it is missing Crystal dependencies.
At least now I know that I may be on the right track. Prior to running the aspnet_regiis.exe, I was getting no error and the same page is being displayed as with my attachment.
Thanks.
you're using crystal reports?
Have a look here for info on deploying applications with crystal.
I'll look into it. Thanks for the link.
I installed my web project on the production server. When running reports, I am getting a "CANNOT FIND KEYCODEV2.DLL OR INVALID KEYCODE" error.
Using this link as a guidline, I proceeded to create a Setup and Development project for an ASP.NET web application (Page 7).
Since I am using a full version of CR9 (replaced CR for VS.NET 2003), I included the ff. files:
Reportenginge.msm
Crnetruntime.msm
License.msm
VC_User_CRT71_RTL_X86_---.msm
VC_User_STL71_RTL_X86_---.msm
I also tried this other link but the registry keys does not exists.
My report is not included when compiling my project. It is being loaded when called and resides on a folder. Debug shows that error occurs at this line code:
The reporting runs fine in the developer machine. Sent email assitance to crystal reports a few minutes ago because I have been running arond in circles the whole afternoon yesterday and until early this morning researching on the web on a possible solution to this problem to no avail.VB Code:
Crystal support asked me to check my crystal references. Version should be 9.2.3300.0 instead of 9.1.5000.0 (CR for VS.NET 2003).
Indeed some of my references are pointing to 9.1.5000.0 so I changed them by removing them from the solution explorer and adding the correct version of references.
The ff. are the list of references I changed:
CrystalDecisions.CrystalReports.Engine
CrystalDecisions.Reportsource
CrystalDecisions.Shared
CrystalDecisions.Web
I changed also all assemblies pointing to 9.1.5000 to 9.2.3300.0 in the webconfig file.
Here's the bummer that I can't figure out why. Once I start to REBUILD the project, my CR references goes back to the old one.
Also, if I save the project with the new references and I exit my VS IDE, when I open the same project, my CR references goes back to the old version.
I'm stumped!
OK. I used this information to solve the problem of my references reverting back to the old version.
It seems that it did the trick. All CR references is now updated to 9.2.3300. I'm happy!
But not for long....now when I run the program, I get this error:
"BC30560: 'CrystalReportViewer' is ambiguous in the namespace 'CrystalDecisions.Web'."
Now, even my developer PC can't run the report! Geeezzeee, this is a never ending Crystal nightmare!!!
I have been troublshooting this crystal nightmare the whole day today. Just when I thought it was over, a new problem pops out.
I checked out this information from Crystal's website to address my 'CrystalReportViewer' is ambiguous in the namespace 'CrystalDecisions.Web' problem. I found some refences to the old version in the web.config and changed them accordingly. I actually made a sweep on my project replacing any references from 9.1.5000.0 to 9.2.3300.0 but the error persists.
Now, just to test everything, I create a new project, add the valid CR references, add a crystal viewer web control to a web form and run it, I get the same error.
That's it for me today!!! Hopefully tomorrow I might get lucky and resolve this problem.
Well, reasons like that make me happy we went with SQL Server 2000 reporting services.
Not that Reporting Services can be used in every situation, since it does require SQL Server 2000, and is mostly helpful for internal enterprise solutions, but man it makes some awesome repors! :)
I feel your pain. I have had each one of those errors myself. I HATE Crystal. I can't even tell you what solved it. Crystal is just a big mess and a pain in the ass to work with in .Net.
I am checking these solutions:
http://www.datadynamics.com/Products...?Product=ARNET
http://www.microsoft.com/sql/reporting/
That is exactly what I was going to say. I haven't used it since version 6, and the only thing I found helpful back then was the fact that it worked with db2. I think that crap was actual 16bit as well. I've refused to use it since then and made sure I didn't install it.Quote:
Originally posted by hellswraith
I HATE Crystal.
I know it probably costs me time but I always feel better when I have a more direct control of whats going on, so I have in the past used generated html and the default web browser for my reproting tool. Ugh, I just had flash backs of a vb reporting app I made that used the vb6 report desiner. It worked and printed, but ugh.
Didn't do much yesterday coz I was on leave. Anyway, going back to the problem on hand.
I uninstaleld CRYSTAL then installed it back again. Well, that was no help since the problem persists.
When I run a project and gets the error, the detailed compiler output shows me that the old version (9.1.5000.0) is being included in the compilation for whatever reason (i think). So I have the new and old version in the compilation.
C:\WINNT\system32> "c:\winnt\microsoft.net\framework\v1.1.4322\vbc.exe" /t:library /utf8output
/R:"c:\winnt\assembly\gac\system\1.0.5000.0__b77a5c561934e089\system.dll"
/R:"c:\winnt\assembly\gac\system.web\1.0.5000.0__b03f5f7f11d50a3a\system.web.dll"
/R:"c:\winnt\microsoft.net\framework\v1.1.4322\temporary asp.net files\crtest_assembly3\c3c2cc58\47d49cc7\assembly\dl2\6a8cbd73\007f3b98_3a34c401\crtest_assembly3.dl l"
/R:"c:\winnt\assembly\gac\system.data\1.0.5000.0__b77a5c561934e089\system.data.dll"
/R:"c:\winnt\assembly\gac\system.drawing\1.0.5000.0__b03f5f7f11d50a3a\system.drawing.dll"
/R:"c:\winnt\assembly\gac\crystaldecisions.web\9.2.3300.0__692fbea5521e1304\crystaldecisions.web.dll"
/R:"c:\winnt\assembly\gac\crystaldecisions.web\9.1.5000.0__692fbea5521e1304\crystaldecisions.web.dll"
So I believe this is where I'm getting the conflict. I went to the GAC folder to remove the old references but it would not let me saying that I cannot uninstall because it is being used by other applications (what other applications???).
I can't remove the reference with the file explorer so used the command prompt to remove it.
Well I was able to remove it but that didn't solve the problem but now I got a new error message something like "missing CrystalDescisions.Web reference for the version 9.1.5000.0". But this time, the compiler output was showing me the exact location of the file I'm getting the error and this is at: c:\inetpub\wwwroot\web.configCode:c:\WINNT\assembly\GAC\CrystalDecisions.Web> rd /s 9.1.5000.0__692fbea5521e1304
I replaced all references to the new version and, well, it worked... Finally!!!
One thing I don't understand though is my project resides on another directory c:\inetpub\wwwroot\RA\. Like I pointed out, the VS IDE shows that the web.config of my project has the latest references and this file is located at c:\inetpub\wwwroot\RA\web.config. This is one folder down from where I was getting the error from.
Anyway, removing the assembly using the command prompt would not be needed if I had known before that I just needed to replace the crystal references on the web.config file. However, I would have not been able to resolve the problem if I have not done so.
Consider this case closed (hopefully).:bigyello:
Can you show your final web.config settings you used?
Here ya go.
PHP Code:<?xml version="1.0" encoding="utf-8"?>
<configuration>
<system.web>
<!-- DYNAMIC DEBUG COMPILATION
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="vb" debug="true"><assemblies><add assembly="CrystalDecisions.CrystalReports.Engine, Version=9.2.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/><add assembly="CrystalDecisions.ReportSource, Version=9.2.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/><add assembly="CrystalDecisions.Shared, Version=9.2.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/><add assembly="CrystalDecisions.Web, Version=9.2.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/><add assembly="CrystalDecisions.ReportAppServer.ClientDoc, Version=9.2.3300.0, Culture=neutral, PublicKeyToken=692fbea5521e1304"/></assemblies></compilation>
</system.web>
</configuration>
Here is crystal's official take on this:
Here's a link on one of their article pertaining to the web.config modifications.Quote:
I'm glad your problem is solved. The reason you had to change settings in the web.config has to do with ASP.NET security settings. Usually asp.net takes its settings from the web.config in the project directory, which overrides any web.config files in higher directories. If one can't be found there, it's taken from a higher directory. Occasionally we see a problem where asp.net ignores the current web.config and takes one from higher up in the directory structure - again, this will depend on how you have your asp.net security set up, and has nothing to do with Crystal Reports itself.
http://support.businessobjects.com/l...s/c2013128.asp