Developed a SAP Crystal Report in ASP.Net 4.0. Works Perfectly in local machine and when hosted in Windows 7 and XP environment. But when deployed the same in client machine the report is not displaying. No error message! it does not show when a click event occurs.
Client machine: Server 2003
Installed: CRforVS_redist_install_32bit_13_0_5 from SAP. on Server
Am I missing something.?
Thanks..
You say there is no error message. Well, if the client machine you are trying to install to has Windows Server 2003, it probably will not have .NET Framework 4 (and above installed). CR 13 requires > .NET 4 to render reports.
I believe that Server 2003 may be too old to run what you want. Take a look at the articles here and here to see how to proceed.
Related
I made my project in C# Visual Studio 2017 using .Net Framework 4.7 and SQL Server 2008. Now I tried to run my project in the client machine which has Windows 10 installed on it. After installing I ran the .exe file, all my functions are running smoothly except my Crystal Reports Viewer.
You need to install SAP runtime for Crystal reports on the client machine
You should have install SQL server on your client machine to make the database working similarly you are required to download the client tool for SAP report. So instal Crystal Report Runtime for client machine and it will let you open your reports on your client machine without any error.
Thanks everyone for your answers but I solved it , the issue was in version of Crystal report as it needed CR V13.0.25.134 for 64 bit but I was using CR V13.0.26 , so yeah I made it through. Thanks again everyone for your time.
I'm developing an ERP via Windows Form Application using (C# and SQL) through Visual Studio 2017 and MSSQL SERVER 2016 (VERSION 852) on a 64 bit Machine with Windows 8.
On deploying the application on the X64 machine with SQLLOCALDB (VERSION 852 or above) installed, the application is working fine.
But, I want to distribute the application in my circles having old machines with X86 (32 bit) architecture. The application is getting installed, but on launching the application, the form with DATABASE CONNECTIVITY is creating a problem.
"The database 'MyFirstWFAAPP' cannot be opened because it is version
852. This server supports version 851 and earlier. A downgrade path is not supported. Could not open new database 'MyFirstWFAAPP'. CREATE
DATABASE is aborted. Cannot attach the file
'C:\devx\2018\MyFirstWFAAPP\App_Data\MyFirstWFAAPP.mdf' as database
'MyFirstWFAAPP'. "
PS: Installation of MSSQL SERVER (Local DB) to 32 bit machines, WINDOW 7, has been deprecated by Microsoft (As I've been informed) So, MSSQL SERVER 2016 and above cannot be installed onto Window 7 systems.
Window 7, XP Support SQL SERVER installation either or below SQL SERVER 2008 R2 (VERSION 660/661).
I'm in a dilemma, as I'm have no idea of what to do.
1) Is there any way, we can convert Code of SQL SERVER 2016 to SQL SERVER 2008 (R2) or below??
2) or, should I delete the MSSQL Server 2016 and then install the 2008 editions.
3) or, should I install SQL 2008 on the parallel with SQL SERVER 2016 running. and, also install MSSQL Server Management Studio and choose the targeted versions of MSSQL. (I'm not sure, whether it's possible. Just guessing).
Please support. As, I'm worried.
Thanks and Regards!
Narayan
This has nothing to do with the target platform (x86 vs. x64). This is simply an issue of targeted SQL Server version. SQL Server knows how to upgrade a database file, but there is absolutely no way it can downgrade one. You are distributing a SQL Server 2016 database file (internal version 852), this will only be opened by the SQL Server 2016 or SQL Server 2017.
But the real problem is different. The real problem is that you are distributing the database as an artifact. This is an absolute NO. Just think how will you distribute the next version of your app, your MDF will replace the actual data that was updated by your 'circles'. You must change your application to distribute only scripts for creating and upgrating database. Your framework of choice may well already provide a solution.
I have a desktop application developed with visual studio 2010, crystal reports, and dot net version 4. The application was installed on the server with sqlserver 2008 as database and was shared over a domain network. On the client side the crystal report shows the login information(SQL authentication) to the server. Once the information is provided it works for two to three times and then shows "login failed for user ....". I went to the services panel on the server and restarted the MSSQL service. The problem resolved but again after two attempts it shows the same error message. Is there a way to resolve this problem instead of keeping on restarting the MSSQL service
SQL server 2008 R2
Dot net v4
MS VS 2010
The Authorization Manager (azman.msc) was deprecated for Windows Server 2012 R2, and it looks as though it might not be in Windows Server 2016.
But I can't find any information regarding Microsoft.Interop.Security.Azroles in Windows Server 2016. Where could I find information about this?
I installed Windows Server 2016 and just installed an application that comes with the Microsoft.Interop.Security.Azroles - library bundled. It worked fine.
azman.msc also still exists in Windows Server 2016.
I don't normally do .NET development but I have a small .NET app that I need to set up on a new Win2K8 IIS 7.5 server, the SQL 2005 server is on a different box. I've tested the .NET app on an Win7 IIS 7/SQL 2005 machine and it works fine. When I run the app on the new server I get the following error:
The 'SQLNCLI11' provider is not registered on the local machine.
I googled the error and found out that I needed to install the native client drivers. I found the sqlncli.msi file on the database server and installed it on the IIS server. Same problem.
I then installed the SQL Management Studio thinking that might have some drivers that it needed. Same error. I can connect through the management studio but the .NET app keeps giving me the same error.
Any suggestions?
Thank!
I changed the provider in my connection string from SQLNCLI11 to SQLNCLI10.
Works like a charm.