Article View: borland.public.cppbuilder.database.multi-tier
Article #1674Re: Deployment Woes
From: John Graham
Date: Fri, 23 Jul 1999 00:00
Date: Fri, 23 Jul 1999 00:00
82 lines
3860 bytes
3860 bytes
Douglas, You don't mention what the remote server's operating system is. The following comments assume you're using NT Server. Windows 95/98 needs another DLL and I'm sorry I don't know the name of it. The server on which you deploy your application server must have STDVCL40.DLL and DBCLIENT.DLL installed in its system32 sub directory and the DLLs must also be registered in the server's registry. You do that by running Borland's TRegSvr.Exe or the Windows equivalent RegSvr32.Exe. You then copy your app server .exe to the machine and run it once. That should register everything. In the client app.'s remote connection object ( DCOM or whatever ) set the Computer Name property to the name of the server where you installed the app. server. Read section 7 of deploy.txt located in you BCB directory. You might also compile and link the EmpEdit example supplied with your package. It works believe it or not. Regards, John Douglas Stites wrote: > I have a working application (3-tier) and when I try to deploy to > non-developement environments, > I have lots of problems. Perhaps some guidance would help. > > What I did: > Server -- Start/register serverapp > stop > Configure broker to localhost > Start -- Broker > Start -- Obj Factory > Export serverapp (note: the interface didn't show > the methodes) > Client > Configure broker to Server > Start obj factory > import serverapp > > ------------ The client sees (sometimes pings the server) ... but > cannot use I get a variety of errors > Please help me understand them > ---------------------------------------------------------------------------- > ---------------------------------------- > 1) The machine was configured, and the broker/obj fact were running on > server. > > Error Msg Unable to load interface for > select object: > The specified object > factory could not be contacted > > The Object factory was running > ---------------------------------------------------------------------------- > ---------------------------------------- > 2) From the Object broker. Try to see interface on imported item. > > Error Msg: Unable to load interface for selected object: Type > Library could not be loaded > > ---------------------------------------------------------------------------- > ---------------------------------------- > 3) From the client. on starting the application: Broker loaded, obj > factory running, connection established > > Error Msg: Error loading type library/DLL > > ---------------------------------------------------------------------------- > ---------------------------------------- > 4) Developement machine, look at the object interface in Object Explorer > ... see all of the properties and methods with their ids. > > Try loading to a second application server, and we dont see the > properties or methods > > What's going on?
Technical Details
Message-ID:
<37987CDC.4F189953@salts.navy.mil>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<7n87ut$n7320@forums.borland.com>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fcd2b,163160f09fa7c5e3 X-Google-Attributes: gidfcd2b,public From: John Graham <jgraham@salts.navy.mil> Subject: Re: Deployment Woes Date: 1999/07/23 Message-ID: <37987CDC.4F189953@salts.navy.mil> X-Deja-AN: 504412707 Content-Transfer-Encoding: 7bit References: <7n87ut$n7320@forums.borland.com> X-Accept-Language: en Content-Type: text/plain; charset=us-ascii Organization: U. S. Navy SALTS Project Mime-Version: 1.0 Newsgroups: borland.public.cppbuilder.database.multi-tier