Assembly on shared drive just doesn't work???

  • Thread starter Thread starter Brett
  • Start date Start date
B

Brett

I have an assembly on a shared LAN drive. On my developer machine, I give
that assembly full trust from the .NET wizard. It works fine. I go to a
user machine on the LAN, map to the shared drive, give full trust on that
machine but the assembly doesn't fully work. No errors. The assembly post
data from MS Access to a website. The posting part doesn't work. The
firewall was turned off and still nothing.

Any ideas?

Thanks,
Brett
 
hi,

do you any logging in the program? did you check the event log?

Does the user machine has access to the server?


cheers,
 
do you any logging in the program?
There isn't any logging. What exactly could I log to help out?
did you check the event log?
Click to expand...
There isn't anything entered that looks as though it relates to this
problem.
Does the user machine has access to the server?
Click to expand...
It is listed in his Windows Explorer and a map was successfully made to a
path on that server. This is where the program is executed from.

The program writes to a text file on the network drive. Then it post data
from an MS Access database to a website. It does successfully write to the
text file on the user machine. If it were a security issue, this shouldn't
happen right?

Any other suggestions are welcome.

Thanks,
Brett
 
Brett said:
There isn't any logging. What exactly could I log to help out?
Click to expand...

Well you could know if you get an exception you will know the line where it
occured. Probably now you are just catch ing it and doing nothing.


The program writes to a text file on the network drive. Then it post data
from an MS Access database to a website. It does successfully write to
the text file on the user machine. If it were a security issue, this
shouldn't happen right?
Click to expand...

How come it does not give you any exception or errors?

That's why my suggestion about logging

Also are you sure that the machine has Jet installed?

Are you using oledb or ODBC ?

Do you have JET installed?


cheers,
 
Brett,

Just to clarify, you are still running the .exe on your user machine...
you're just loading it from a shared drive, right? It works when you
run it from a local copy, but not when you invoke the same executable
on the same machine, but loading it from a shared drive. Is this
accurate?
 
Ignacio Machin ( .NET/ C# MVP ) said:
Well you could know if you get an exception you will know the line where
it occured. Probably now you are just catch ing it and doing nothing.




How come it does not give you any exception or errors?

That's why my suggestion about logging

Also are you sure that the machine has Jet installed?

Are you using oledb or ODBC ?

Do you have JET installed?
Click to expand...

I'm using oledb. How can I be sure JET is installed?
 
Bruce Wood said:
Brett,

Just to clarify, you are still running the .exe on your user machine...
you're just loading it from a shared drive, right? It works when you
run it from a local copy, but not when you invoke the same executable
on the same machine, but loading it from a shared drive. Is this
accurate?
Click to expand...

No. The EXE is on a server. Two machines map a J drive to the server. My
developer machine executes the EXE fine. The user machine doesn't. No
errors. The prog writes to a text file but it will not post MS Access data
to a website. All of that works on my developer machine.

Thanks,
Brett
 
Brett said:
No. The EXE is on a server. Two machines map a J drive to the server.
My developer machine executes the EXE fine. The user machine doesn't. No
errors. The prog writes to a text file but it will not post MS Access
data to a website. All of that works on my developer machine.

Thanks,
Brett
Click to expand...

Yes, the exe is on the share but it runs on the client's machine. As Ignacio
said, you have to make sure all components to access the Access files
(loacted on the same share?) are installed on the client.
As there's no exception thrown when trying to open the DB, I suppose that
accessing the DB is not an issue, remains the question what you mean exactly
with post to the webserver, and where is the server located (same as the
exposing the share?).
What kind of application is this (console, Windows Forms?).

Willy.
 
Willy Denoyette said:
Yes, the exe is on the share but it runs on the client's machine. As
Ignacio said, you have to make sure all components to access the Access
files (loacted on the same share?) are installed on the client.
As there's no exception thrown when trying to open the DB, I suppose that
accessing the DB is not an issue, remains the question what you mean
exactly with post to the webserver, and where is the server located (same
as the exposing the share?).
Click to expand...

The DB, text file and EXE are all in the same directory on a shared drive.
DB writes an ID # to the text file. The EXE reads an ID # from the text
file. It uses this ID # to access a table in the DB and writes that to a
CSV file. The CSV is then POSTed to remote website. A FORM POST is used via
httpResponseArray = myWebClient.UploadFile(strPost, "POST", FileName)
 
Brett said:
The DB, text file and EXE are all in the same directory on a shared drive.
DB writes an ID # to the text file. The EXE reads an ID # from the text
file. It uses this ID # to access a table in the DB and writes that to a
CSV file. The CSV is then POSTed to remote website. A FORM POST is used
via
httpResponseArray = myWebClient.UploadFile(strPost, "POST", FileName)

WinForm.
Click to expand...

Is the CSV file created? If it is, you might have a security issue when
posting to the webserver, again this should throw an exception unless you
swallow them :).

Willy.
 
Willy Denoyette said:
Is the CSV file created? If it is, you might have a security issue when
posting to the webserver, again this should throw an exception unless you
swallow them :).

Willy.
Click to expand...

I can't run the app just yet but what type of security issue on that one
machine may exists?

Thanks,
Brett
 
Hi,

I'm using oledb. How can I be sure JET is installed?
Click to expand...

IIRC the newer versions of MDAC does not include the JET provider, you can
download it from MS site.

Now, I would implement a logging of each steps, somewhere it has to fail and
give you an exception or an error code. It seems to be in the POST upload,
as you said that it created the file correctly.
Does the web require auth?
What if you just do a WebRequest , just to see if you have access to it

Still, I think you are catching an exception somewhere and doing nothing
about it.



cheers,
 
Back
Top