problem with ReportViewer - vb.net

I make a program using vb.net and the report I am using ReportViewer. but when i install the client computer that uses XP, the reports can not be accessed and the error message appears. please help

Probably you have to install the Report Viewer Redistributable on the client's computer.

Related

MDAC Error on Windows XP - Deploy Vb.net

I am trying to deploy a VB.Net application using the built in Click Once.
When a User tries to install the application they receive the following error message.
http://i.imgur.com/6ifvdKM.png
The machines they are trying to install to are Windows XP SP3 so I cant understand why I am getting this error.
Any help would be appreciated.
You should try the following steps:
Compile your program and copy the whole bin\Release folder (output directory) to the target system. Does your program run if it's not distributed via ClickOnce?
Build a simple "Hello World!" program and distribute it via ClickOnce. Can this basic app be installed on the target system by running the ClickOnce installer?
Even though this should not be a problem on any system running a later Version of Windows than Win2k, have your tried to just install Microsoft Data Access Components (MDAC) 2.8 SP1?
By doing so, you should be able to determine if your issue is either ClickOnce- or Application-related.

how to deploy crystal report on client machine, in vb.net

I am working on VB.net project with Crystal report.
My problem is that, on the client's machine Crystal report forms are failing with the following error;
Error-> "Either the crystal report registry key permissions are
insufficient,or the crystal reports run time is not installed
correctly"
Any idea how to solve the issue please?
you need to install crystal report viewer only to client PC, not the whole software just the viewer.
depends on client PC 64 bit or 32 bit, and the version has been developed with.

How to install CR10 runtime on win7 64bit

I'm using the Crystal Report 10 viewer ActiveX control in an Access App I've written. Works great in Office 2003 on 32bit versions of Windows. The problem arrises when I try to run the program in 64 bit Windows (with 32bit Office). I get the following error:
Run-time error '429': ActiveX component can't create object
I get this error on the following line of my VBA code.
Set rdApp = CreateObject("Crystalruntime.application.10")
How can I get this to work in 64bit?
I don't have any specific experience with Crystal Report, but I do have some experience with installing components on a 64-bit Windows environment that were intended for 32-bit Windows, so here are some general suggestions of things to try:
Before installing, try loosening the security privileges - I have Windows Server 2008; on this OS, they're under Start | Administrative Tools | Local Security Policy. Many old installers are thwarted by these controls. You'll want to return them to their defaults after the install.
Make sure that you run the installer with admin privileges (right-click; run as Administrator).
Examine the installation log for Crystal Report - it may indicate a failure registering a component. In one instance, I was able to get the installation working by running the command to register the failed component manually, on an administrator-privileged command line (the command was in the log).
If acceptable, try to create a Windows Virtual Machine running a virtual Windows XP, and try the installations there (this might be a bit tedious, due to your need for MS Office).
Take a look at VMWare's ThinApp - this is intended for packaging applications for administrators, but this was the solution we ended up using to shield one of our 32-bit apps from Windows 64-bit perils
Hope this helps; we struggled for awhile trying different things to get our legacy apps working on a 64-bit environment.

How do I resolve "Run-time error '429': ActiveX component can't create object"?

My company has a VB6 application using Crystal Reports 7 which a client has asked to be installed on Windows 7 32 bit. It is currently installed on Windows XP 32bit SP2 machines at the client. Connection to the DB is done via ODBC to SQL Server 2000 instance on another server.
On Windows 7, the installation works fine, however when you try to open the application, the error is given.
I have looked at the following:
Registering all the dll's and ocx files using regsvr32. Some will not register as they either are registered already or the following message is given "Make sure that "[name].dll" is valid DLL or OCX file and then try again." I read this forum thread regarding this: http://social.msdn.microsoft.com/forums/en-US/vblanguage/thread/0653f685-4526-45d9-89f3-8c479a6b4c62
Monitored the opening of the application using a ProcessMonitor application to try and spot if there is a missing dll or ocx file - this does not seem to be the case.
Reviewed the application according to this list and nothing seems to be against these guidelines
I've noticed two items in the knowledge base that relate to this
http://support.microsoft.com/kb/281848 - the comdlg32.ocx bundled with the application is version 6.0.81.69 and the one in the system32 folder on the dev machine (WinXP 32 bit) is 6.1.97.82. However if this was the issue then surely it would not work currently?
http://support.microsoft.com/kb/184898 - I'm not sure how to confirm that this is the issue
Finally, due to complexities, I am not allowed to make code changes to this application. Even if I was, I'm not a VB6 programmer, just the guy who got the terribly support project! If code changes are required, then I'll have to investigate using WinXP mode.
Update: I get the same error in XP Mode. That's a Win XP with SP3 VM. This runs on a Win XP SP2 VM, is there potentially something in SP3 that would have caused this to occur? Or is it just a fact of it being XP Mode?
I got the same error but I solved by using regsvr32.exe in C:\Windows\SysWOW64.
Because we use x64 system. So if your machine is also x64, the ocx/dll must registered also with regsvr32 x64 version
The file msrdo20.dll is missing from the installation.
According to the Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7 this file should be distributed with the application.
I'm not sure why it isn't, but my solution is to place the file somewhere on the machine, and register it using regsvr32 in the command line, eg:
regsvr32 c:\windows\system32\msrdo20.dll
In an ideal world you would package this up with the redistributable.
This download fixed my VB6 EXE and Access 2016 (using ACEDAO.DLL) run-time error 429. Took me 2 long days to get it resolved because there are so many causes of 429.
http://www.microsoft.com/en-ca/download/details.aspx?id=13255
QUOTE from link:
"This download will install a set of components that can be used to facilitate transfer of data between 2010 Microsoft Office System files and non-Microsoft Office applications"
You say it works once you install the VB6 IDE so the problem is likely to be that the components you are trying to use depend on the VB6 runtime being installed.
The VB6 runtime isn't installed on Windows by default.
Installing the IDE is one way to get the runtime. For non-developer machines, a "redistributable" installer package from Microsoft should be used instead.
Here is one VB6 runtime installer from Microsoft. I'm not sure if it will be the right version for your components:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7b9ba261-7a9c-43e7-9117-f673077ffb3c

TABCTL32.OCX(1.1.0)

I am trying to upgrade a VB6 project to run it on VB8, but I am getting an error which says that you need to install TABCTL32.OCX(1.1.0).
What shall I do? Please Help.
Thanks in advance.
To run the upgrade wizard you need VB6 installed on the machine, and also any controls used in the code you are upgrading.
Tabctl32.ocx is the Tabbed Dialog Control 6.0, the standard tab control from VB6. If you install VB6 you will be fine.
See Microsoft's list of controls shipped with Visual Basic 6.