Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 247
  • Last Modified:

Error : Object server not correctly registered.

HI,

I have developed a simple visual Basic application. It is Reporter and it uses Crystal report 4.0, GRaph control, TrueGrid control, etc. When I prepare my distribution media using InstallShield Express ver. 2.0, it shows me a message like "Could not find windows registry information for Olepro32.dll. You will have to add file manualy." THen I am adding file using explorer. When I install my software on the Windows NT 4.0, It always gives me an error 336 "Object Server not correctly registered". In that system, I have not installed any kind development tools. It is a fresh Windows NT Server.

When I prepare my diskettes using Application WIzard of Visual Basic, I am able to prepare diskettes and I can successfully execute that application. I have One big application and I want to have one installation CD. SO that it is easier for user to install. My one module is VC++ 5.0 and other is Visual Basic 4.0. THis application is on WIndows NT 4.0, Visual Basic 4.0, Crystal Report 4.0 and TrueGrid Ver. 4.0

I would really appreciate your suggestion and guidelines.

Byr,
Dipesh Shah
0
dipesh042997
Asked:
dipesh042997
  • 2
1 Solution
 
dirtdartCommented:
All dlls your program uses have to be registered with Windows.  That is, the information concerning that dll (where it is, what it is, etc) has to be stored in the registry.  Most dlls and custom controls you deal with have the ability to self register, but you have to initiate this.  When using the VB Setup Wiz, this is done automatically for you because the Setup Wiz can create a list of files your program needs to run.  During your setup routine, it then calls the appropriate functions for the dlls to self register.  You can also force InstallShield to do this, but you have to write custom script for it, and I am not familiar enough with InstallShield to talk you through this.  However, as an intermediate step to solving your problem, try this.

After using InstallShield to install your app, make a list of the dlls that were installed on the target machine.  Then use regsvr32.exe (provided with Visual Basic) to manually register the dlls.  The format would look like this:

regsvr32 dllname

where dllname is the full qualified path and name of the dll, including extension.  This will cause the dll to register itself with the Windows registry and will then be accessable to your program once again.

0
 
dipesh042997Author Commented:
My application is using Microsoft Jet Engine. Do  I need to register dao3032.dll files also ?  I tried one thing. Previously my diskettes did not contain dao3032.dll. After lots of debugging I found out that it is missing. SO I copied that file from another machine. But it did not work. So do I need to register that also ?
0
 
dirtdartCommented:
Yes, the dao3032.dll also needs to be registered.  EVERY dll that your program uses needs to be registered.  If you have any doubt about a component, try to register it anyway.  If it doesn't need to be registered, regsvr will just give you an error, and no harm will be done.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now