Customer Service can update images on the Webserver.

This is achieved by using the CopyFile Method of the Scripting FileSystemObject via OLE. This was used because any other method of copying OS files from OI v8.07 would update the time/date stamps of the files which need to be left intact.

This worked fine when the webserver was on the same LAN that the server hosting OI was on. However Customer Service was moved to Ohio (along with the OI application). The webserver still resides in Los Angeles.

The UNC has been updated to reflect any changes.

Now when the Form script is executed to perform the copy OLEStatus returns a code of -2147352567.

I'm guessing it is an access/rights problem. We do not want map a shared drive to the user workstations. Read files into a BITMAP control is no problem using the same UNC.

Is there a simple solution to this?

I rather not setup an engine on webserver just to run a simple task like this.

TIA

Can you do the file copy by hand as one of the app users?

What happens if you write a small script to perform the CopyFile method? Does it succeed? This would help determine if the problem is rights related because it would occur outside of OI. If it succeeds then I'd question the integration with OI.

Besides the server changing locations what has changed? New domain? Did the share rights change?

I'd recommend writing a test VBScript to prove the methods and variables are correct - then compare it with what OI us feeding into the OLE control.

Hi Jared

I'll try running a VBSCRIPT outside of OI a try and see what happens.

Let me detail the setup:

Webserver - Win2000 Server - no domain

LA Server - Win2003 Server - LA domain

OH Server - Win2003 Server - OH domain

The Web and LA servers are connect on a LAN

OH Server connects to above via WAN (VPN).

Data is mirrored between the LA and OH servers via a MFS over the WAN. Prior to moving Customer Service to OH the all the edits and updates were done on the LA server, with the OI Forms set to basically read-only. The read-only status was toggled for the move so that LA became read-only and edits and updates are done on the OH server. The UNC was changed to use an IP address rather than the server name but still points to the LA server.

The Domain has changed but only because the edits are now done on the OH domain.

Ok, I figured it out finally.

A configuration record didn't get updated and copied over. The file was not mirrored since until now none of the webserver operation were done in OH. Oversight.

View this thread on the Works forum...