>Trying to work with existing system in SQL Server2000. Brand new VB.NET project for reporting purposes. PDC is off of NT4 box.
>
>When I connect I am using the sa identity and I fail :(
>
>error comes back as "[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied. "
>
>This is from the stack trace:
>
>[OleDbException (0x80004005): [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.]
> System.Data.OleDb.OleDbConnection.ProcessResults(Int32 hr)
> System.Data.OleDb.OleDbConnection.InitializeProvider()
> System.Data.OleDb.OleDbConnection.Open()
> System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState)
> System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
> System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
> System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable)
> OakLeaf.MM.Main.Data.mmDataAccessOleDb.FillDataSet(DataSet ds, IDbDataAdapter dbAdapter, String tableName, Boolean clearOnFill)
> OakLeaf.MM.Main.Data.mmDataAccessOleDb.FillDataSet(DataSet ds, IDbCommand command, String tableName, Boolean clearOnFill)
> OakLeaf.MM.Main.Data.mmDataAccessOleDb.FillDataSet(DataSet ds, String command, String tableName, CommandType cmdType, IDbDataParameter[] dataParms, Boolean clearOnFill)
> OakLeaf.MM.Main.Business.mmBusinessObject.FillDataSet(DataSet ds, String command, String tableName, String databaseKey, CommandType cmdType, IDbDataParameter[] dataParams)
> OakLeaf.MM.Main.Business.mmBusinessObject.FillDataSet(DataSet ds, String command, String tableName, String databaseKey, IDbDataParameter[] dataParams)
> OakLeaf.MM.Main.Business.mmBusinessObject.FillDataSet(DataSet ds, String command, String tableName, String databaseKey)
> OakLeaf.MM.Main.Business.mmBusinessObject.FillDataSet(DataSet ds, String command, String tableName)
> TGI.Reporting.Business.ClubBiz.BuildReOrderReport(String strEntryDateBegin, String strEntryDateEnd) in C:\Documents and Settings\SRussell.TGI\My Documents\Visual Studio Projects\TGI_Reporting Business\ClubBiz.vb:39
> TGI.Reporting.Club1.cmbRunReport_Click(Object sender, EventArgs e) in c:\inetpub\wwwroot\TGI_Reporting\Club1.aspx.vb:63
> System.Web.UI.WebControls.Button.OnClick(EventArgs e)
> System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument)
> System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument)
> System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData)
> System.Web.UI.Page.ProcessRequestMain()
>
>Is the problem that machinename/ASPNET is doing the conncetion, and they are not understood in the PDC back in NT4 days??
>
>TIA

Stephen,
I don't think this has to do something within MM itself. PDC is known in NT4 days but since you're using sa/pwd you're not using PDC at all (which is not recommended). You're using SQL server authentication. Is necessary libraries loaded for SQL server? Is it listening on a TCP port? Is it configured for default port? What's your connection string (except pwd itself)?
A typical connection that works:

server=x.x.x.x,port;uid=sa;pwd=password

x.x.x.x represent IP address of server and port port# that SQL server is listening on. You can check port# from SQL server's log (and many other places).

I don't suggest using sa/pwd in the first place. Check PAG documentation for granting ASPNET access to SQL server (or a mirrored account). Unfortunately sa/pwd approach is shown in almost every example.

Also check if firewall settings permit access to SQL server.
Cetin