Issue Connecting To An Ms Access Database

[Dtentchoff]

Up till a day or so ago we had no issue connecting to one of our MS Access database. Since then, we have been recieving the following error message:

strError='\\Vana_albuc1s\Albuc1\groups\nihb\vision.vb\vis_alb.mdb' is not a valid path. Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

The server is a Netware OES 10 server. The connection exists and the pathing is correct. Any suggestions about where to look ay next?

 

Dave

0115_1118_vgEngine.txt

[SupportTeam]

Most likely this is caused by some security feature limiting access to remote directories by services etc.

 

Was any anti-virus etc. software installed recently on any of the systems involved?

 

Another approach would be to setup an ODBC connection to the database.

Set up and test the ODBC connection (you may need to download the appropriate drivers - Searching Google for "ms access odbc driver" should being up more information) and then have VoiceGuide use the created ODBC connection.

 

 

 

111937.546  6   5   3 state [Provider Type] DB Query
111937.546  6   5   3       rv    replace start [select tblProvider.ProviderType_id from tblprovider where tblProvider.Provider_Number = '$RV[Provider Number]']
111937.546  6   5   3       rv    replace end   [select tblProvider.ProviderType_id from tblprovider where tblProvider.Provider_Number = '1073390']
111937.546  6   5   3       db    strDatabaseName=[system.Data.OleDB] strDbConnectString=[Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\Vana_albuc1s\Albuc1\groups\nihb\vision.vb\vis_alb.mdb;] sAdoNetFactoriesAvailable=[|System.Data.Odbc|System.Data.OleDb|System.Data.OracleClient|System.Data.SqlClient|VistaDB.NET20|System.Data.SQLite|]
111937.546  6   5   3       db    using default ado.net OleDb data provider: OleDbConnection/OleDbCommand/etc
111937.546  6   5   3 t     timer set   40 sec : EV_TIMEOUT_GOTOMODULE
111937.546  6   5   3       strDirOfDb=, altering strDatabaseName to: C:\scripts\System.Data.OleDB
111937.546  6   5   3       db    oledb RunQuery_OleDb Provider Type, C:\scripts\System.Data.OleDB, Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\Vana_albuc1s\Albuc1\groups\nihb\vision.vb\vis_alb.mdb;, select tblProvider.ProviderType_id from tblprovider where tblProvider.Provider_Number = '1073390'
111937.546  6   5   3       db    oledb RunQuery_OleDb blob - none
111937.546  6   5   3       db    oledb thread init.
111937.546  6   5   3       db    oledb thread started.
111937.546 23   5   3       db    oledb ConnectAndRun_OleDb begin. Create connection: [Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\Vana_albuc1s\Albuc1\groups\nihb\vision.vb\vis_alb.mdb;]
111937.546 23   5   3       db    oledb connection open call [Provider=Microsoft.Jet.OLEDB.4.0;Data Source=\\Vana_albuc1s\Albuc1\groups\nihb\vision.vb\vis_alb.mdb;]
111937.609 22   5   3       db    oledb ConnectAndRun_OleDb thread completed.
111937.703 23   5   3 ERROR v7.2.4050.41622 (2011-02-02 23:07:25.26) ConnectAndRun_OleDb init : '\\Vana_albuc1s\Albuc1\groups\nihb\vision.vb\vis_alb.mdb' is not a valid path.  Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.

  at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
  at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
  at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
  at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
  at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
  at System.Data.OleDb.OleDbConnection.Open()
  at ..()
111937.703 23   5   3       oVgmDbQuery_AdoNetCommon_Completed SqlQueryType=, RowsCount=0, sRv=
111937.703 23   5   3       oVgmDbQuery_AdoNetCommon_Completed strError='\\Vana_albuc1s\Albuc1\groups\nihb\vision.vb\vis_alb.mdb' is not a valid path.  Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.
111937.703 23   5   3       path {'\\Vana_albuc1s\Albuc1\groups\nihb\vision.vb\vis_alb.mdb' is not a valid path.  Make sure that the path name is spelled correctly and that you are connected to the server on which the file resides.} not found
111937.703 23   5   3       path {ERROR} not found
111937.703 23   5   3       HangupCall, source=oVgmDbQuery_AdoNetCommon_Completed ERROR, WorkModeScript=Running_Normal, yLineStateAppPov=[Connected], lPlayId=0, lRecId=0

[Dtentchoff]

I am still having connection issues.

Checked/found the following:

NIVR account - logs into Novell, maps correct drives, has the correct rights.

Voiceguide has a connection to the VANA_ALBUC1S server.

The NIVR system runs a IVR (Voiceguide) as a service.

Voiceguide can access local databases and databases on shared Windows drives.

When Voiceguide tries to access the Novell drive, it generates "path ('\\Vana_albuc1s\Albuc1\groups\nihb\vision.vb\vis_alb' is not a valid path. Make sure that the path is spelled correctly and that you are connected to the server on which the file resides." error message in Voiceguide.

 

Checked path - is correct. Generates the same error message if the path is spelt incorrectly.

ODBC connections generate the same error.

 

When the vgIvrService.exe tries to connect to the database, it calls on the NetwareRedirector to resolve the name. Voiceguide gets the error listed above in the calls log file. Using Process Monitor, the NetwareRedirector generates a BAD NETWORK NAME error.

 

We are running the Novell Client 4.91 SP5 for Windows(IR1) and the version of the vgIvrSerive is 7.0.9.0.

Any ideas what might be causing this?

Is there a newer version of the Voiceguide appplication?

[SupportTeam]

The "not a valid path" error is issued by the database connector/provider (System.Data.OleDB).

 

Looks like the database providers and ODBC drivers call the NetwareRedirector.

 

If you say that you can see that the NetwareRedirector return a BAD NETWORK NAME error then you should contact Novell, or people who configure/maintain Novell Netware on your system to resolve this.

 

Updating VoiceGuide would not change how Novell Netware works on your system.

 

You may want to check what access privileges Novell Netware gives to the VoiceGuide service, or if it generally restricts Windows Services in any way.

VoiceGuide service usually runs under a Local System account.

 

You say that :

Up till a day or so ago we had no issue connecting to one of our MS Access database.

What was changed immediately prior to inter-server connectivity being lost?