[Last Call] Learn how to a build a cloud-first strategyRegister Now

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

Open a form, get E_FAIL error, lose network drive...

Hi,

I have an ADP - Access 2000 front-end, SQL Server 2000 back-end.

When I sit at our file server and open the ADP, and then open up an Access form called OrderForm, I get the following error: "Data Provider or other service returned an E-FAIL status."  When I click "OK" -- the Microsoft "failure acceptance" button that makes everything all better -- most of the form fields are then populated with #Error.

Here's an interesting twist:  When the E_FAIL error is encountered on the server, the networked "G" drive, located on the server, becomes unavailable to users elsewhere on the network... Although the "G" drive *is* still available to me, since I'm still at the server itself.

I have no clue why these two occurences are even related.  But mainly, I have no clue as to why I am (suddenly) getting the E_FAIL error message to begin with.  Can anyone help me?  I don't even know what it means.  SQL Server is working just fine.

--Galisteo8
0
Galisteo8
Asked:
Galisteo8
2 Solutions
 
Galisteo8Author Commented:
Oh... One more thing.
When the E-FAIL occurs while the OrderForm is opening up, at the bottom by the nav buttons where it usually displays the number of records being loaded into the recordset, it just says, "0..."
0
 
rburelloCommented:
Did you check the ODBC connection information?  Does it use a system/file DSN or is it DSN less?  If you are using a DSN, check to make sure it is connecting properly.
0
 
netcoolCommented:
Hi

I have seen this error E-FAIL when connecting from Access from Oracle, The E-Fail occur due to the network problem. The network is trying to disconnect the link, what you can do try to use the ping command from the command prompt to see the network link to your server.

This is purely network problem.

 
0
Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Galisteo8Author Commented:
rburello,

How/Where would I check the ODBC connection information?  I am not certain I can do that, as I am not the server admin...

netcool,

The problem occurs only when I am actually working on the server itself.  The ADP file is on the server, Access runs on the server, and it accesses the SQL database on the server.  I agree that it must be some kind of issue with the server or maybe network drivers.... but I just have no idea how, when the problem is, in essence, "local" to the server itself.
0
 
jjafferrCommented:
Are you the owner of the ADP Or the Admin?
This sounds like Record Locking by the owner of the ADP or the Admin.

Try this,
Let another user open the ADP first, then you open it while the other one is still open, your ADP will work ok.

jaffer
0
 
SidFishesCommented:
...jjafferr... i'm sure you meant

"Let another user open -their copy of the- ADP first, then you open it while the other one is still open, your -copy- ADP will work ok."

cause as we know adp's are not multiuser capable...each client needs thier own or you'll get the famous Has been locked for editing warning... ;)

my question to Galisteo would be why are you working on a production server...bitter experience has shown me the light...this is a bad thing to do...let the server -serve- i know that sometimes it's hard to justify dedicating a box but it really is the only safe way to go...

Quote: "Doctor...It Hurts when I do this"
           "Well then don't do that"





0
 
rburelloCommented:
today I received an E-Fail message when trying to launch a shortcut from a vbs script using the shell object.  I searched for information on the E_FAIL message and did not find anything.  

Has this worked in the past? If so, have there been any updates to the server.

--------------
The ODBC connection is under the adminitrator tools.  Do you have access to the code on the access database?  Does the Access database work on other workstations?
0
 
Galisteo8Author Commented:
Yes, I am the admin of the ADP.

No, I am not the admin for the server.

rburello,
I do have access to the code on the Access database.  And, Yes, the ADP works just fine on other workstations.

Sid,
No option but to work on the production server, generally.  Although -- now that you mention it -- I could work on one of the staff's PC's since I'm only on-site in the evenings now.  I could implement and test my changes to a copy of the ADP on the workstation, then copy that ADP to the G drive on the server (which is a public drive) so that other users could copy it to their own workstations from there.
0
 
rburelloCommented:
Does the server have a G drive and is it the same as the users?
0
 
Galisteo8Author Commented:
rburello,

The server machine has a G drive. It is not an actual disk drive, but rather just a virtual drive.  All the employees' workstations map to it with the "G" designation, and it is a public drive.  When I make changes to the ADP file, I put the new version on the G drive so that users can find it and copy it to their local workstations.

The SQL Server and the location of all the SQL data is NOT on the drive, but rather on a different drive on the server machine.
0
 
rburelloCommented:
You stated that the G: is a virtual drive.  I do not understand that, did you mean a mapped drive or a SAN drive?.  If its a mapped drive you should not be sharing it, that would explain why the workstations get nock off the G:.  The SQL data does not matter what drive it is on.  SQL data is retrieved with code in the front-end database using DSN or DSNless connections.  

I still think that there is a DSN issue on the server, check the following

On Workstation:
     start -> settings -> control panel -> administrator tools -> ODBC connection

     Click system DSN tab and look for a DSN that connects to the database
     If you can not file one than click on the file DSN tab and look for one

     If you find it then create an ODBC connection on the server using the information from the workstation.  If you do not find one that open the ADP database holding down the shift key.  Goto Tools -> Database Utilites -> Linked table manager.  Click on Select All button and click OK.  A popup box should come up that states the name of the data source and should ask for a username and password.  Enter the information and click OK.  You will  have do this for every table.  If you get any errors, please post them.


0
 
Galisteo8Author Commented:
I'm not certain, but I believe G is simply a mapped drive.  However, the E-FAIL errors and workstations getting knocked off is only a *recent* problem.  The G drive has not been altered in any way for at least a year.

"create an ODBC connection on the server using the information from the workstation" -- how/where is this done?


0
 
rburelloCommented:
start -> settings -> control panel -> administrator tools -> ODBC connection

you should look at the workstations first to see if there is one there.  
0
 
Galisteo8Author Commented:
I'll try to do that tomorrow evening, since I'll be at that client site.
0
 
Galisteo8Author Commented:
Haven't had a chance to analyze as per rburello's suggestion yet.  However, one of the staff discovered a seemingly related issue while working alone on a Saturday afternoon.  She was using the Access ADP stored on her desktop PC.  Intermittently, and inconsistently, while saving a new record from one of the Access forms, she encountered timeouts and errors.  After closing error messages and returning to the form to view that record, some information she had entered might be missing -- or it might not.

Ultimately, this is sounding like a server issue to me -- the actual Win2000 server, not the SQL Server -- and not necessarily a connection issue.  What do you think?
0
 
Galisteo8Author Commented:
Sorry about that.  I believe that the situation was server- or network-related (i.e. out of my domain), and it seems to have been resolved.

If it is okay with all concerned, I'll go ahead and close and distribute points among the responders.  I will attempt to do so in an equitable manner, although since the problem dissipated of its own accord, I am not certain what any one suggestion might have proved helpful.
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

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