Monday, December 14, 2009

Load report failed windows 98 crystal report .net c#.net vb.net

Load report failed

If we are depoying a windows application created in Visual studio dot net which is using crystal reports the error may occure as "Load report failed".

The reason for this error message is Dbghelp.dll is missing in the computer which is running windows 98. The dll called crqu.dll is depends on dbghelp.dll.


To resolve this problem you must include dbghelp.dll in the setup package for your windows application project.After you deploy the application on a computer that is running Windows 98 and that has the .NET Framework installed, copy the Dbghelp.dll file to the folder where the Crqe.dll file is located.


The Crqe.dll file is located in the following folder on your computer that has Visual Studio .NET installed:

%Program Files%\Common Files\Crystal Decisions\1.0\Bin




Reference for this blog is

http://support.microsoft.com/kb/837219

Sunday, December 13, 2009

An error occurred during client rendering.,An error has occurred during report processing.,The connection is not open.,Query execution failed for data

If using sql server reporting service and the report's datasource connected to Microsoft Sql Server 2008 Analysis services. When you are opening the report by using a non-administrative account you may receive different error messages. The error messages will vary depends on credential settings of datasource in report manager

In case of windows integrated security

If you are using windows integrated security you will receive the following error messages.

A) An error occurred during client rendering.

B) An error has occurred during report processing.

C) Query execution failed for dataset ''.

D) The connection is not open.

If your report manager configuration does not require any credentials error message will be

The current action cannot be completed. The user data source credentials do not meet the requirements to run this report. Either the user data source credentials are not stored in the report server database, or the user data source is configured not to require credentials but the unattended execution account is not specified. (rsInvalidDataSourceCredentialSetting)

If your configuration is like stored securely in the report or using Os credentials when connecting datasource or impersonate authentication or the user specified have sufficiant permissions the message will be as of first case.

Reasons

When you open the report, the data source of the report connects to SQL Server 2008 Analysis Services by using the data source credential. After the connection is established, successive requests to SQL Server 2008 Analysis Services do not reuse the data source credential. Instead, successive requests use the credential of the current user. This causes the problem that is mentioned in the "Symptoms" section.

Ref : http://support.microsoft.com/kb/973588

Solution


You must use SQL Server 2008 Service Pack 1 (SP1) to fix this problem



HAPPY PROGRAMMING

Friday, December 11, 2009

Error message when you install SQL Server 2005 SP2, SQL Server Express SP2, or SQL Server Express with Advanced Services SP2: "SQL Server Setup failed

A web application that attempts to create a database or read/write to a database using SQL Server Express user instance mode can encounter any of the following errors:

Error message when you install SQL Server 2005 SP2, SQL Server Express SP2, or SQL Server Express with Advanced Services SP2: "SQL Server Setup failed to execute a command for server configuration. CREATE DATABASE failed"

A web application relies on SQL Server Express' user instance mode if either of the following is true:

The application relies on the default "LocalSQLServer" connection string defined in machine.config
The application uses a connection string that contains the following attributes:

"AttachDBFilename=|DataDirectory|xxxxxx.mdf;User Instance=true"

Resolution for Web Application Projects and Websites

For web application projects (WAP) and websites located in a user's Documents Folder hosted under any version of IIS running as NETWORK SERVICE, carry out the following steps:

First confirm that IIS has been configured to run as NETWORK SERVICE. This is the default on IIS6 and IIS7. However if you are running on Windows 7 or Window Server 2008 R2 you will first need to follow the steps above in "Resolution for Windows 7 and Windows Server 2008 R2" to make IIS application pools run as NETWORK SERVICE.
From a command prompt, type net stop iisadmin /y . This will cause any running ASP.NET WAP applications to shutdown.
Exit out of all running Visual Studio instances.
NETWORK SERVICE must be granted Read permission to the top-level Visual Studio folder located in your user's Documents folder. The Visual Studio folder will have different names depending on the version: "Visual Studio 2005", "Visual Studio 2008", or "Visual Studio 2010".
NETWORK SERVICE must be granted both read and write permissions to your project's top-level project folder. For example if your WAP project is called "MyCustomWebProject", then the folder "Documents\Visual Studio 20xx\Projects\MyCustomWebProject" needs to have read and write access enabled for NETWORK SERVICE. Or, if your webiste project is called "MyCustomWebProject", then the folder "Documents\Visual Studio 20xx\Websites\MyCustomWebProject" needs to have read and write access enabled for NETWORK SERVICE.
NETWORK SERVICE must be granted both read and write permissions to the App_Data folder located within your web project's directory structure.

You should provide default values for all form fields that are used in the query.

The following error may come when you are trying to install sql server express edition on computer running windows vista


SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Windows NT user or group 'COMPUTERNAME\SQLServer2005MSSQLUser$COMPUTERNAME$MSSQLSERVER' not found. Check the name again.. Refer to the server error logs for detailed error information.


This problem occurs if the following conditions are true:
The Windows Vista-based computer has a name that consists of lowercase characters or that consists of a mixture of lowercase characters and uppercase characters. For example, the computer name resembles Workstation-1.
You specify a case-sensitive collation setting for the SQL Server service when you install SQL Server 2005 Express Edition SP1.
Windows Vista uses the following two methods to return the computer name in response to a request for the computer name:
Windows Vista can return the computer name in uppercase characters.
Windows Vista can return the computer name in the actual mixed case characters that appear in the System Properties dialog box.
During one part of the installation of SQL Server 2005 Express Edition, the Setup program requests the computer name as mixed characters. However, Windows Vista returns the computer name in uppercase characters instead. The Setup program also requests the computer name in other parts of the installation of SQL Server 2005 Express Edition. Windows Vista may then return the computer name in mixed case characters.

The SQL Server 2005 Express Edition Setup program compares the received computer names. Generally, this does not cause a problem because computer names are not case sensitive in Windows Vista. However, if a case-sensitive collating sequence is specified when you install SQL Server 2005 Express Edition, the result of the name comparison between the computer name in uppercase characters and the computer name in mixed case characters fails. Therefore, the installation of SQL Server 2005 Express Edition SP1 is unsuccessful.

Method 1: Change the computer name to use only uppercase characters
A computer name is not case sensitive in Windows. For example, Windows recognizes "Workstation-1" and "WORKSTATION-1" as the same computer name. To change the computer name, follow these steps:
Click StartCollapse this imageExpand this image, right-click Computer, and then click Properties.
Under Computer name, domain, and workgroup settings, click Change settings.

Collapse this imageExpand this imageIf you are prompted for an administrator password or for a confirmation, type your password, or click Continue.
In the System Properties dialog box, click Change.
In the Computer name box, note the original computer name, and then type a temporary computer name in uppercase characters. For example, type WORK-TMP.
Click OK.

Note If you are prompted to enter the name and password of a domain account that has permission to rename the computer, type your credentials, and then click OK.
When you are prompted to restart the computer to apply the changes, click OK, click Close, and then click Restart Now.
Follow steps 1 through 6 to change the computer name to the original computer name. When you specify the original computer name, type the name in uppercase characters. For example, type WORKSTATION-1 instead of Workstation-1.
Install SQL Server 2005 Express Edition SP1.

Method 2: Use a case-insensitive collation setting for the SQL Server service
When you install SQL Server 2005 Express Edition SP1, do not select a case-sensitive collation setting. For more information about how to select the collation setting when you install SQL Server 2005 Express Edition SP1, see the following Microsoft SQL Server 2005 Books Online topics:

One or more form fields were empty. You should provide default values for all form fields that are used in the query.

After you use the Database Interface Wizard to create a Database Editor Web page, you may receive an error message similar to the following:

Database Results Error
Description: [Microsoft][ODBC Microsoft Access Driver] Syntax error in UPDATE statement.
Number: -2147217900 (0x80040E14)
Source: Microsoft OLE DB Provider for ODBC Drivers

One or more form fields were empty. You should provide default values for all form fields that are used in the query.


OR

Database Results Error
Description: [Microsoft][ODBC Microsoft Access Driver] Field 'Table Name. Field Name' cannot be a zero-length string.
Number: -2147467259 (0x80004005)
Source: Microsoft OLE DB Provider for ODBC Drivers

One or more form fields were empty. You should provide default values for all form fields that are used in the query.



where Table Name is the table in the database, and Field Name is the field in the database.

This problem can occur if you attempt to update a database record that has an empty field. The setting for the database column does not allow zero-length entries.

To resolve this issue, make sure that all data fields that do not allow zero-length entries are populated before you submit the form.

To work around this issue, start Microsoft Access and then open the database table in Design view. Set the Allow Zero Length attribute to Yes for each field that you want to allow blank entries.

Sunday, November 29, 2009

Login failed for user sa crystal report

Hi


Login failed for user sa

In his “Troubleshooting Database Login Errors using Crystal Reports with .NET,” Eric Landes points out that he sees questions regarding the “Exception Details: CrystalDecisions.CrystalReports.Engine.LogOnException: Logon failed” message quite often in the newsgroups. That's an understatement. Since I use the “push” method (generating an ADO.NET dataset first, then setting the report's DataSource), I never saw this error, but I decided to try and replicate the problem to see why this was happening--it seems to be a popular error. I had a suspicion that impersonation and the “double hop“ (where the ASP.NET application cannot pass the user's credentials) may play a role in this problem, since the methods in Eric's article don't solve the problem for every user it should.

To replicate the problem, I used an ASP.NET project connecting to either a remote production SQL Server database or a copy of the same database on my development machine (SQL Server Developer Edition). I created a stored procedure that was just a simple SELECT statement, and used this stored procedure as my report source (“pull“ method). I probably created this report 20 different ways, testing various options, and here's what I found.

Saturday, November 28, 2009

Error on Sum in Formula Field, crystal reports , formula ,sum

Error on Sum in Formula Field

When using a formula or expression field to perform a calculation of a set of numbers, you may receive the following error message
!Syntax Error, xxx,xxx
where xxx represents the numbers in the argument.

This error occurs when two or more numbers are separated by a comma without a space and the second and subsequent numbers are three or more digits. For example, the following expressions
{=sum(123,123)}
{=sum(123,123,123)}
will produce the following errors:
!Syntax Error, 123,123
!Syntax Error, 123,123,123
This behavior occurs when the formula field performs the following calculations: SUM, AVERAGE, MIN, MAX, and PRODUCT.

If the expression contains a series of three or more numbers, the second number is one or two digits, and each number is separated by a comma without a space, your results will be inaccurate, and you will not get a syntax error. For example, the following expression
{=sum(1,22,222,222)}
will produce the following result:
22,222,223
This behavior does not occur when you perform calculations based on table cell references or when using bookmarks.

When the comma is not followed by a space but is followed by three digits, Word interprets the comma as being the thousands-place separator and treats the argument as one number.

Place a space immediately following the comma, so that your formula looks as follows:
{=SUM(123, 125)}