Cant get Access Database Synchronizer set up on client machine

I have created a PPC application that uses ADS to synchronize my sqlce db with a desktop MS Access database. It works fine on my computers, but my client cant get it to work on his. Here is the situation.

His "Computer Name" as it's stated in his 'My Computer' properties is "PAVSGP024FE.NWFSC.NOAA.GOV"

However his Access.MDW File is located in the directory "C:\Documents and Settings\Joe Nobody\Application Data\Microsoft\Access\System.MDW".

There is no directory called "C:\Documents and Settings\PAVSGP024FE.NWFSC.NOAA.GOV\Application Data\Microsoft\Access\System.MDW".

His current config.xml file looks like this.

<?xml version="1.0" encoding="UTF-8"?>
<SystemNode>
<AccessDB>C:\Program Files\NOAA Release Logger\NOAA_ReleaseLogger.mdb</AccessDB>
<DeviceDB>\Program Files\NOAA Release Logger\NOAA_ReleaseLogger.sdf</DeviceDB>
<Login>Joe Nobody</Login>
<URL>http://Joe Nobody:1024/</URL>
<WinDir>C:\</WinDir>
</SystemNode>

He has tried adding port 1024 as an exception for his firewall settings, has installed Access Database Synchronizer on his computer, and I have also tried using the "long" computer name as the url setting in the config file. (i.e. <URL>http://PAVSGP024FE.NWFSC.NOAA.GOV:1024/</URL> but this throws the error

"The HTTP request failed due to incorrect format or content. Try restarting the IIS server.[]"

I dont know what else to try! Anybody have any suggestions?

I have had the same problems when I first installed. THen for some reason things started working. Now a few weeks later, when I get back to trying it, no work anymore. I suggest you read the readme.doc that comes with it. THere are some things to check there. Make sure IIS is running. THen you add a 1024 port if you have the firewall enabled. I also had some success when I manually copied the .cab file to the device, then installed that way. I don't think I have ever got it to work just downloading the sample project.

Another thing to verify is that your internet connection is going from device to desktop. Open IE and try to open http://<computer>:1024/. Presently, I am unable to do this so I think something is wrong on my Desktop platform. I am going to try another platform that used to work.

|||

Tried to run the synchronizer on the other platform that it used to work on also. Now that one is not working either. I went through all the steps I know of to get it working, no luck. I cannot get the IE to link up to the web service either which I am thinking must be the main problem.

I am sorry to say, I need to give up trying to get it to work now.

|||

Wanted to check, have you got it running now.

Please note: You do not IIS to run ADS applications. Stop the IIS and try.

The path of the .msw file should be C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW.

So if his user name on the computer is "Joe Nobody" then specify the path as "C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW" as indicated in your post.

|||

We did finally get this working but, only because we gave up installing it on this particular computer. His computer was part of a business network and something about it would not allow this to work. Once he installed everything on a non-network computer everything worked as it should. So, unfortunately, we never did actually get to the root of this particular problem.

Mike

Cant get Access Database Synchronizer set up on client machine

I have created a PPC application that uses ADS to synchronize my sqlce db with a desktop MS Access database. It works fine on my computers, but my client cant get it to work on his. Here is the situation.

His "Computer Name" as it's stated in his 'My Computer' properties is "PAVSGP024FE.NWFSC.NOAA.GOV"

However his Access.MDW File is located in the directory "C:\Documents and Settings\Joe Nobody\Application Data\Microsoft\Access\System.MDW".

There is no directory called "C:\Documents and Settings\PAVSGP024FE.NWFSC.NOAA.GOV\Application Data\Microsoft\Access\System.MDW".

His current config.xml file looks like this.

<?xml version="1.0" encoding="UTF-8"?>
<SystemNode>
<AccessDB>C:\Program Files\NOAA Release Logger\NOAA_ReleaseLogger.mdb</AccessDB>
<DeviceDB>\Program Files\NOAA Release Logger\NOAA_ReleaseLogger.sdf</DeviceDB>
<Login>Joe Nobody</Login>
<URL>http://Joe Nobody:1024/</URL>
<WinDir>C:\</WinDir>
</SystemNode>

He has tried adding port 1024 as an exception for his firewall settings, has installed Access Database Synchronizer on his computer, and I have also tried using the "long" computer name as the url setting in the config file. (i.e. <URL>http://PAVSGP024FE.NWFSC.NOAA.GOV:1024/</URL> but this throws the error

"The HTTP request failed due to incorrect format or content. Try restarting the IIS server.[]"

I dont know what else to try! Anybody have any suggestions?

I have had the same problems when I first installed. THen for some reason things started working. Now a few weeks later, when I get back to trying it, no work anymore. I suggest you read the readme.doc that comes with it. THere are some things to check there. Make sure IIS is running. THen you add a 1024 port if you have the firewall enabled. I also had some success when I manually copied the .cab file to the device, then installed that way. I don't think I have ever got it to work just downloading the sample project.

Another thing to verify is that your internet connection is going from device to desktop. Open IE and try to open http://<computer>:1024/. Presently, I am unable to do this so I think something is wrong on my Desktop platform. I am going to try another platform that used to work.

|||

Tried to run the synchronizer on the other platform that it used to work on also. Now that one is not working either. I went through all the steps I know of to get it working, no luck. I cannot get the IE to link up to the web service either which I am thinking must be the main problem.

I am sorry to say, I need to give up trying to get it to work now.

|||

Wanted to check, have you got it running now.

Please note: You do not IIS to run ADS applications. Stop the IIS and try.

The path of the .msw file should be C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW.

So if his user name on the computer is "Joe Nobody" then specify the path as "C:\Documents and Settings\"User Name"\Application Data\Microsoft\Access\System.MDW" as indicated in your post.

|||

We did finally get this working but, only because we gave up installing it on this particular computer. His computer was part of a business network and something about it would not allow this to work. Once he installed everything on a non-network computer everything worked as it should. So, unfortunately, we never did actually get to the root of this particular problem.

Mike

Can't Find SQL Native Client in ODBC Connection Manager in SQL Server Open Database Connectivit

I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.

I am running Windows XP Pro SP2. I have installed the SQL Native Client for

XP. However, when I try to add a new data source through ODBC Connection

Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the

SQL Native Client to not show up in the list of available ODBC data sources?

Hi, James,

First of all - are you sure that the installation of the SQL Native Client completed successfully? Do you see the packet in the Add/Remove Programs applet? What you can try first is to uninstall (if available) and reinstall the Client, check if any errors or warnings would be reported.

Going further - the ODBC drivers information is stored in the registry. Using regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI and check if the SQL Native Client driver is present, the entries in the folder as well as an entry at "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers" folder.

If the SQL Native Client driver is not present in the registry, you might have a permission issue. One possible approach is to run and capture a RegMon log during the installation (http://www.microsoft.com/technet/sysinternals/SystemInformation/Regmon.mspx) and see if access to the key above failed.

If the SQL Native Client driver is present in the registry, then for some reason the ODBC Administrator fails to enumerate it or it contains invalid entries. First step would be to compare the entries to a "working" machine and then you could probably use RegMon again - this time when running ODBC Administrator.

Based on the findings, you could take corrective actions and start seeing the driver properly.

HTH,

Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks for the reply. SQL Native Client does appear in Add/Remove programs, and I am able to uninstall and reinstall. I will do the other checks you mentioned, and let you know the results. Thanks.|||

I am having a very similar problem. I am using Visual C++ 2005 Express and have installed the Microsoft SQL Server Native Client. All the mentioned registrty entries appear to be correct. I have also include all of the ODBC components in my toolbox. When I try to configure the ODBC data adpater, create a new connection, the only types of data sources that are in the possible list are the SQL Server and Access. If I add an OdbcConnection tool to the form and try to modify the connection string to a new connection, I get a message that the data provider identified by guid "all zeroes" could not be loaded. It would appear that csomething is missing.

I have tried to find a "Data" component to reference in the project that might include the missing component, but have had no success.

Can't Find SQL Native Client in ODBC Connection Manager in SQL Server Open Database Connectivit

I apologize if this is not the correct forum for this posting. Looking at the descriptions, it appeared to be the best choice.

I am running Windows XP Pro SP2. I have installed the SQL Native Client for XP. However, when I try to add a new data source through ODBC Connection Manager, SQL Native Client is not listed as an option. I have followed this procedure on three other systems with no problems. What would be causing the SQL Native Client to not show up in the list of available ODBC data sources?

Hi, James,

First of all - are you sure that the installation of the SQL Native Client completed successfully? Do you see the packet in the Add/Remove Programs applet? What you can try first is to uninstall (if available) and reinstall the Client, check if any errors or warnings would be reported.

Going further - the ODBC drivers information is stored in the registry. Using regedit, go to HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI and check if the SQL Native Client driver is present, the entries in the folder as well as an entry at "HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC Drivers" folder.

If the SQL Native Client driver is not present in the registry, you might have a permission issue. One possible approach is to run and capture a RegMon log during the installation (http://www.microsoft.com/technet/sysinternals/SystemInformation/Regmon.mspx) and see if access to the key above failed.

If the SQL Native Client driver is present in the registry, then for some reason the ODBC Administrator fails to enumerate it or it contains invalid entries. First step would be to compare the entries to a "working" machine and then you could probably use RegMon again - this time when running ODBC Administrator.

Based on the findings, you could take corrective actions and start seeing the driver properly.

HTH,

Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks for the reply. SQL Native Client does appear in Add/Remove programs, and I am able to uninstall and reinstall. I will do the other checks you mentioned, and let you know the results. Thanks.
|||

I am having a very similar problem. I am using Visual C++ 2005 Express and have installed the Microsoft SQL Server Native Client. All the mentioned registrty entries appear to be correct. I have also include all of the ODBC components in my toolbox. When I try to configure the ODBC data adpater, create a new connection, the only types of data sources that are in the possible list are the SQL Server and Access. If I add an OdbcConnection tool to the form and try to modify the connection string to a new connection, I get a message that the data provider identified by guid "all zeroes" could not be loaded. It would appear that csomething is missing.

I have tried to find a "Data" component to reference in the project that might include the missing component, but have had no success.

sql

Can't Find SQL Native Client in ODBC Connection Manager

I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this
procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?MDAC issues, related DLL conflicts. The ODBC Data Source
Administrator piece can get hosed out with DLL conflicts on
an MDAC installation. You'd probably want to start checking
the MDAC installation using component checker. You can
download it from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 13 Feb 2007 10:31:01 -0800, Jim Strickland <Jim
Strickland@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>I am running Windows XP Pro SP2. I have installed the SQL Native Client for
>XP. However, when I try to add a new data source through ODBC Connection
>Manager, SQL Native Client is not listed as an option. I have followed this
>procedure on three other systems with no problems. What would be causing th
e
>SQL Native Client to not show up in the list of available ODBC data sources?[/vbcol
]

Can't Find SQL Native Client in ODBC Connection Manager

I am running Windows XP Pro SP2. I have installed the SQL Native Client for
XP. However, when I try to add a new data source through ODBC Connection
Manager, SQL Native Client is not listed as an option. I have followed this
procedure on three other systems with no problems. What would be causing the
SQL Native Client to not show up in the list of available ODBC data sources?
MDAC issues, related DLL conflicts. The ODBC Data Source
Administrator piece can get hosed out with DLL conflicts on
an MDAC installation. You'd probably want to start checking
the MDAC installation using component checker. You can
download it from:
http://msdn2.microsoft.com/en-us/data/aa937730.aspx
-Sue
On Tue, 13 Feb 2007 10:31:01 -0800, Jim Strickland <Jim
Strickland@.discussions.microsoft.com> wrote:

>I am running Windows XP Pro SP2. I have installed the SQL Native Client for
>XP. However, when I try to add a new data source through ODBC Connection
>Manager, SQL Native Client is not listed as an option. I have followed this
>procedure on three other systems with no problems. What would be causing the
>SQL Native Client to not show up in the list of available ODBC data sources?

Cant find SMSS

After installing the evaluation edition of MSSQL Enterprise 2005 I can not find SSMS. I know I installed the client tools upon installation. It's not showing up on in the menu, where is the location for the executable file.

Is SSMS even distriubted with the evaluation edition?

If not, is it possible to download it from somwhere...

Did you get any warnings while setup cheked your computer configuration?

Did you specify client tools installation during setup?

P.S. This question suits http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=95&SiteID=1 forum better.

|||

SSMS is part of the evaluation edition. To see a report of what's installed go to Add/Remove Programs, select the entry for "Microsoft SQL Server 2005", select "Change", then select "Report". Under "Common Components" you'll want to see something like this:

Workstation Components
[Version: 9.00.1399.06 Edition: Evaluation Edition Patch level: 9.00.1399.06 Language: English (United States)]

If you see this and still don't think you have SSMS installed, close the report. On the "Change" dialog you should see an entry for Workstation Components, select it and press "Next". This will launch the component in maintenance mode. Just follow the dialogs. When you get to the feature tree be sure to select Management Tools under the Client Components node.

SSMS is installed to %ProgramFiles%\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\sqlwb.exe

|||Thanks for your reply::

I got the evauation to work when I downloaded the DVD image and burnt it to disk, and did a fresh install...

I'm now in the process of converting my MySQL talbles over to MSSQL... weeee fun... SSIS takes some of the headake away!|||Excellent!

Can't find client

I can't see any SQL Management tools after installed SQL 2005. How can I see
the database by tools just like what we had in SQL 2000?
Hello,
Run the Setup program when you continue you have an option for Components to
install and choose "Workstation COmponents"
and continue.
Thanks
Hari
"Kit Wong" <Kit Wong@.discussions.microsoft.com> wrote in message
news:6CA37313-603E-4275-A714-E6491EA13408@.microsoft.com...
>I can't see any SQL Management tools after installed SQL 2005. How can I
>see
> the database by tools just like what we had in SQL 2000?
|||Hari,
Thanks. I can see and select workstation components and client components.
But it hhas been ceased with error immediately.
TITLE: Microsoft SQL Server 2005 Setup
There was an unexpected failure during the setup wizard. You may review the
setup logs and/or click the help button for more information.
For help, click:
[url]http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server& ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=50000& EvtType=packageengine%5cinstallpackageaction.cpp%4 0InstallToolsAction.10%40sqls%3a%3aInstallPackageA ction%3a%3aperform%400x643[/url]
BUTTONS:
OK
COACH [pizza01@.netvigator.com]
"Hari Prasad" wrote:

> Hello,
> Run the Setup program when you continue you have an option for Components to
> install and choose "Workstation COmponents"
> and continue.
> Thanks
> Hari
>
> "Kit Wong" <Kit Wong@.discussions.microsoft.com> wrote in message
> news:6CA37313-603E-4275-A714-E6491EA13408@.microsoft.com...
>
>
|||Hello,
See the Setup bootstap log folder (Program Files\Microsoft SQL
Server\90\Setup Bootstrap\LOG) for the setup log file and see if there is
any
error occured during installation.
Thanks
Hari
"Kit Wong" <KitWong@.discussions.microsoft.com> wrote in message
news:0BBA2865-ABD7-481B-9809-3FCC48D49193@.microsoft.com...[vbcol=seagreen]
> Hari,
> Thanks. I can see and select workstation components and client components.
> But it hhas been ceased with error immediately.
> TITLE: Microsoft SQL Server 2005 Setup
> --
> There was an unexpected failure during the setup wizard. You may review
> the
> setup logs and/or click the help button for more information.
>
> For help, click:
> [url]http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server& ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=50000& EvtType=packageengine%5cinstallpackageaction.cpp%4 0InstallToolsAction.10%40sqls%3a%3aInstallPackageA ction%3a%3aperform%400x643[/url]
> --
> BUTTONS:
> OK
> --
>
> COACH [pizza01@.netvigator.com]
> "Hari Prasad" wrote:

Can't create SSIS project in BIDS on workstation with Client tools only installed

I have the June CTP SQL 2005 client tools only installed on my workstation. All has gone well until I tried to create a SSIS project in BIDS.

I receive this message

TITLE: Microsoft Visual Studio

Error creating package

ADDITIONAL INFORMATION:

Failed to save package file "D:\Documents and Settings\SuzMSDN\Local Settings\Temp\tmp13E.tmp" with error 0x80040154 "Class not registered".

Failed to save package file "D:\Documents and Settings\SuzMSDN\Local Settings\Temp\tmp13E.tmp" with error 0x80040154 "Class not registered".

Tried registering DTSPipeline.dll per a post with no success.

I can log into the server where SQL is installed and use BIDS on the server without issue for an SSIS project.

Thoughts?

Susan

Does the dialog have "show technical details" button?
If yes, please post this information.

Thanks,
Michael.|||

Below are the technical Details ...thanks

Susan
===================================

Error creating package (Microsoft Visual Studio)

===================================

Failed to save package file "D:\Documents and Settings\SuzMSDN\Local Settings\Temp\tmp10.tmp" with error 0x80040154 "Class not registered".

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)
at Microsoft.DataTransformationServices.Wizards.Dts90WizardSaveNewTask.AddPackageToProject(Package package, String itemName)
at Microsoft.DataTransformationServices.Wizards.Dts90WizardSaveNewTask.CreateAndAddPackageToProject()
at Microsoft.DataTransformationServices.Wizards.Dts90WizardSaveNewTask.Execute(WizardInputs wizardInputs)

===================================

Failed to save package file "D:\Documents and Settings\SuzMSDN\Local Settings\Temp\tmp10.tmp" with error 0x80040154 "Class not registered".

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToXML(String FileName, IDTSPersist90 pPersistObj, IDTSEvents90 pEvents)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToXml(String fileName, Package package, IDTSEvents events)

|||Let's try this:

regsvr32 msxml3.dll
regsvr32 msxml4.dll
regsvr32 msxml6.dll|||Michael,

Thanks you. That did the trick. I had to unregister msxml6 in order to take the MS SQL 2005 elearning classes.

So to take class you unregister...to work you register. ; )

Hopefully corrected for elearning in the next release.

Thanks for your assistance.

Susan

Can't create excel file with SQL Server 2000 client.

Hi ;

I am trying to create several Excel sheets using SQL 2000 views like so:

Select * INTO [Excel 8.0;Database="C:\spreadSheets\aNew.xls"] FROM [aView].

When I try and execute this in my app I get the following - Specified owner
name 'Excel 8.0;Database=c:\spreadSheets\aNew.xls' either does not exist or
you do not have permission to use it.

If I use the above Select statement with an OLEDB connection it works.

I am using Imports System.Data.SqlClient, instantiating a new SQlConnection
object, opening the connection, etc..

Thanks,

Gordon

This special select into sql statement syntax only works if you use the Jet OLEDB Provider, it's not supported by SQL Server.

So you need to open a connection to some Access database (even a dummy one will work) and do something like this:

I wrote this KB article about a decade ago (arg where does the time go) that demos the syntax:

200427 How To Export and Import Access Tables Using DAO or ODBC
http://support.microsoft.com/default.aspx?scid=kb;EN-US;200427

Here is some demo code that uses .NET:

System.Data.OleDb.OleDbConnection conn;

System.Data.OleDb.OleDbCommand cmd;

conn = new System.Data.OleDb.OleDbConnection(@."Provider=Microsoft.Jet.OLEDB.4.0;Data Source=c:\junk.mdb;");

conn.Open();

cmd = conn.CreateCommand();

cmd.CommandType = CommandType.Text;

cmd.CommandText = "select * into [Excel 8.0;Database=C:\\Book1.xls;].[MyJunk] FROM [ODBC;Driver=SQL Server;Server=mySQLServer;Database=Pubs;Trusted_Connection=Yes;].[authors]";

cmd.ExecuteNonQuery();

However note there are tons of annoyances with using Jet driver and Excel, the Jet and Excel teams just never seem to want to make this any easier for the customer. The other way to do this is poke values into Excel speadsheet using ole automation (which used to be easy cheesy in VB6 but now is a nightmare in .NET since .NET deprecated COM). With newer version of Excel 2007 I wonder maybe this is easier in .NET.

Can't connect with Upgrade Advisor

I'm having trouble connecting the Upgrade Advisor to a SQL 2000 box at a client. Here's the setup:

1> I'm running UA on a Virtual PC image

2> I can run UA against other SQL machines on the same domain

3> I can register and administer the SQL server I'm having trouble with in Enterprise Manager

4> I have SA rights on the SQL box I'm having trouble with.

5> The problem is when entering the server name and clicking "detect," it errors out with "The network path not found (mscorlib)."

6> I've tried server name, FQDN and IP address.

This is a fairly convoluted layout, so there could be a firewall issue that I'm not aware of (but I don't think so).

Any help would be appreciated!

Bob

Bob, have you tried running UA directly on the target server? It shouldn't be a problem unless the OS level on the server doesn't support UA.|||

Hey, Allen. Thanks for the feedback...as we discussed Thursday (but I mention here in case anyone else is interested), I don't want to add the .Net Framework to the server at this point.

Bob

Cant connect via EM after changing sa password?

A client of mine changed his SA password "because it hadn't been changed in a while". :mad: Now nobody can get into Enterprise Manager - opening EM or trying to right-click > Connect on the server yields an error:

A connection could not be established to SERVER1.

Reason: login failed for user 'sa'.

Please verify SQL Server is running and check your SQL Server Registration
properties (by right-clicking on the SERVER1 node) and try again.

Of course, if I right-click on the SERVER1 node, I get the same message.

My client remembers the password he set; I managed to use it to get into Query Analyzer, which I thouhght was weird. But no luck with Enterprise Manager. It's just trying to log in as sa without prompting for a pw.

I already tried running sp_Password in Query Analyzer to change the pw back to what it was. Still can't connect to the SQL Server via Enterprise Manager.

What can I do?Did you edit the sql server registration and change the password there?

EDIT: And while I'm Here

Now nobody can get into Enterprise Manager

SCARY

Sorry Rudy|||Unclear from your post: have you tried editing the connection properties, or are you not able to get to that point?

If it won't even let you right-click on the registration to edit the properties, then try dropping the registration and creating a new one.|||Unless BUILTIN\Administrators local group is removed from SQL Server security, you can logon as a local admin or as a member of that group and easily change the SA password.

Cant connect to sql server 2000 from asp.net

I installed sql server 2000 on a remote server. I can connect toit from the client with query analyzer, but I cannot connect to it fromASP.NET. I'm using Sql authentication, and the account has everypermission under the sun. I can also connect to it from theserver explorer in visual studio.net. I turned off thefirewall. I tried connecting with the same asp.net code from adifferent computer and still no luck. I've triple-double-checkedthe connectionstring. It's the same credentials I'm using forquery analyzer and server explorer, which both work fine. Anytroubleshooting tips would be GREATLY appreciated.

Thank you.What error message are you receiving?|||The problem ended up being with the version of .net I was using. I hadinstalled 1.1 initially, but someone installed commerce server 2002 andit installed .net 1.0 on top of that, which messed everything up. I reinstalled windows 2003 and then reinstalled .net 1.1, and all isgood.

Cant connect to sql 2000 from client with all field available i.e server ip and port

cant connect to sql server 2000 from c# 2003

Hi,

Could you please post more information on the specific error and conditions? Please take a look at the following guideline:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=362498&SiteID=1

In addition, how are you providing the IP address and Port? As per Books Online the format should be:

tcp:<IP Address>[\instancename],<port>

HTH,
Jivko Dobrev - MSFT
--
This posting is provided "AS IS" with no warranties, and confers no rights.

Can''t connect to local Report server, error code....

Anyone know how to get around this?

TITLE: Connect to Server

Cannot connect to OES-XP1007.

ADDITIONAL INFORMATION:

Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<html>
<head>
<title>
SQL Server Reporting Services
</title><meta name="Generator" content="Microsoft SQL Server Reporting Services 9.00.3054.00" />
<meta name="HTTP Status" content="500" />
<meta name="ProductLocaleID" content="9" />
<meta name="CountryLocaleID" content="1033" />
<meta name="StackTrace" content />
<style>
BODY {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE: 8pt; COLOR:black}
H1 {FONT-FAMILY:Verdana; FONT-WEIGHT:700; FONT-SIZE:15pt}
LI {FONT-FAMILY:Verdana; FONT-WEIGHT:normal; FONT-SIZE:8pt; DISPLAY:inline}
.ProductInfo {FONT-FAMILY:Verdana; FONT-WEIGHT:bold; FONT-SIZE: 8pt; COLOR:gray}
A:link {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR3366CC; TEXT-DECORATION:none}
A:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLORFF3300; TEXT-DECORATION:underline}
A:visited {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; COLOR3366CC; TEXT-DECORATION:none}
A:visited:hover {FONT-SIZE: 8pt; FONT-FAMILY:Verdana; colorFF3300; TEXT-DECORATION:underline}

</style>
</head><body bgcolor="white">
<h1>
Reporting Services Error<hr width="100%" size="1" color="silver" />
</h1><ul>
<li>An internal error occurred on the report server. See the error log for more details. (rsInternalError) <a href="http://go.microsoft.com/fwlink/?LinkId=20476&EvtSrc=Microsoft.ReportingServices.Diagnostics.Utilities.ErrorStrings&EvtID=rsInternalError&ProdName=Microsoft%20SQL%20Server%20Reporting%20Services&ProdVer=9.00.3054.00" target="_blank">Get Online Help</a></li><ul>
<li>Could not find stored procedure 'GetOneConfigurationInfo'.</li>
</ul>
</ul><hr width="100%" size="1" color="silver" /><span class="ProductInfo">SQL Server Reporting Services</span>
</body>
</html>
--. (Microsoft.SqlServer.Management.UI.RSClient)

BUTTONS:

OK

Please see this thread:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1955241&SiteID=1

Someone else has a similar problem to yours.

Can't connect to Distributor

Hello,
I am trying to set up transactional replication between a server (that is both the distributor and publisher) and a client (msde). The server (sql2000) is configured for mixed mode authentication - windows & sql. Our client subscribers will be using a
nonymous pull subscriptions...so they are not part of our domain.
We have a vb.net application and I am using the code from http://support.microsoft.com/default...;en-us;Q319648 as a starting point. The only changes I made to the sample code was to change the SECURITY_TYPE.NT_AUTHENTICATION to DB_AUTHENTICATI
ON and add my login and password.
I cannot get past the "Process could not connect to Distributor "SERVER" error.
As a quick test...I ran a trace with SQL Profiler...and there isn't even a login attempt. I can ping the server from my client/subscriber.
Is there something else I am missing? I searched through some of the archives and none of the suggestions have worked for me so far.
Thanks
DD,
have you set up an alias in the client network utility on the client
computer? This article may help any other settings:
http://support.microsoft.com/default...22&Product=sql
Regards,
Paul Ibison
|||I did not set up an alias on the client. I didn't think that this step was necessary because we are replicating(well, trying) over the internet via ftp. We will have many clients and I didn't know if we will have to set up this alias.
I read through that article and went through the pieces that had to do with replicating over the internet with ftp. I have everything set according to those documents. One thing..HOWEVER...I actually cannot ping the server. The network admin turned off
or disabled ping on that server. I can go to a command prompt and type "ftp myserver.mydomain.com" and get to the ftp prompt. My question now is...by disabling the ability for machines outside our network and firewall to ping the server...does this me
an that replication won't work even though ftp has been enabled?
"Paul Ibison" wrote:

> DD,
> have you set up an alias in the client network utility on the client
> computer? This article may help any other settings:
> http://support.microsoft.com/default...22&Product=sql
> Regards,
> Paul Ibison
>
>
|||if you can't ping try tracert. or ftp.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"DD" <DD@.discussions.microsoft.com> wrote in message
news:0FA8DD44-B9D6-48E9-8AA9-0478322F6B6B@.microsoft.com...
> I did not set up an alias on the client. I didn't think that this step
was necessary because we are replicating(well, trying) over the internet via
ftp. We will have many clients and I didn't know if we will have to set up
this alias.
> I read through that article and went through the pieces that had to do
with replicating over the internet with ftp. I have everything set
according to those documents. One thing..HOWEVER...I actually cannot ping
the server. The network admin turned off or disabled ping on that server.
I can go to a command prompt and type "ftp myserver.mydomain.com" and get to
the ftp prompt. My question now is...by disabling the ability for machines
outside our network and firewall to ping the server...does this mean that
replication won't work even though ftp has been enabled?[vbcol=seagreen]
> "Paul Ibison" wrote:
http://support.microsoft.com/default...22&Product=sql[vbcol=seagreen]
|||Well...I can go to a command prompt and connect to the server with:
ftp MyServer.Domain.com
If this is enough to indicate that a pull subscription should be able to connect to the server...then I am not sure what else to look at to resolve this issue.
I suppose I could remove the publication, disable replication and start over again.
"Hilary Cotter" wrote:

> if you can't ping try tracert. or ftp.
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "DD" <DD@.discussions.microsoft.com> wrote in message
> news:0FA8DD44-B9D6-48E9-8AA9-0478322F6B6B@.microsoft.com...
> was necessary because we are replicating(well, trying) over the internet via
> ftp. We will have many clients and I didn't know if we will have to set up
> this alias.
> with replicating over the internet with ftp. I have everything set
> according to those documents. One thing..HOWEVER...I actually cannot ping
> the server. The network admin turned off or disabled ping on that server.
> I can go to a command prompt and type "ftp myserver.mydomain.com" and get to
> the ftp prompt. My question now is...by disabling the ability for machines
> outside our network and firewall to ping the server...does this mean that
> replication won't work even though ftp has been enabled?
> http://support.microsoft.com/default...22&Product=sql
>
>
|||no, no, no, go to your publisher, and in
c:\%windir%\system32\logfiles\MSFTPSVC look for the log file with today's
date stamp and locate entries that correspond to your attempt to connect.
There will be some numbers associated with the attempt, check this link out
to see what the error codes mean
http://www.4d.com/docs/CMU/CMU88906.HTM
Look in the FTP RFC Values section
This will tell you exactly why you are failing.
"DD" <DD@.discussions.microsoft.com> wrote in message
news:EB413FD6-D8AD-4128-80EA-CF7C95C34602@.microsoft.com...
> Well...I can go to a command prompt and connect to the server with:
> ftp MyServer.Domain.com
> If this is enough to indicate that a pull subscription should be able to
connect to the server...then I am not sure what else to look at to resolve
this issue.
> I suppose I could remove the publication, disable replication and start
over again.[vbcol=seagreen]
> "Hilary Cotter" wrote:
step[vbcol=seagreen]
via[vbcol=seagreen]
up[vbcol=seagreen]
ping[vbcol=seagreen]
server.[vbcol=seagreen]
get to[vbcol=seagreen]
machines[vbcol=seagreen]
that[vbcol=seagreen]
http://support.microsoft.com/default...22&Product=sql[vbcol=seagreen]
|||Thanks for the correction. I am still trying to figure this one out...but as a quick test, I changed the settings for the user login and password from the one I had been using (a sql long with limited access) to the "sa" account...and it works great. S
o...there must be some sort of permission problem I need to wrangle with. I have noticed since that server was updated from Win2K server to Win2003 Server...the security access/permissions have been tightened down and many things that use to work...no lo
nger.
"Hilary Cotter" wrote:

> no, no, no, go to your publisher, and in
> c:\%windir%\system32\logfiles\MSFTPSVC look for the log file with today's
> date stamp and locate entries that correspond to your attempt to connect.
> There will be some numbers associated with the attempt, check this link out
> to see what the error codes mean
> http://www.4d.com/docs/CMU/CMU88906.HTM
> Look in the FTP RFC Values section
> This will tell you exactly why you are failing.
> "DD" <DD@.discussions.microsoft.com> wrote in message
> news:EB413FD6-D8AD-4128-80EA-CF7C95C34602@.microsoft.com...
> connect to the server...then I am not sure what else to look at to resolve
> this issue.
> over again.
> step
> via
> up
> ping
> server.
> get to
> machines
> that
> http://support.microsoft.com/default...22&Product=sql
>
>
|||DD,
I am having the same problem here. It's stuck in the Snapshot Agent's connecting attempt to the distributor. It's not even related to Subscription. It just give up during initializing snapshot.
The distributor_admin and sa password are set to the same and mapped in remote_server login.
The only thing I haven't tried is restart the MSSQL and SQLAgent because all my clients are using the databases.
Posted using Wimdows.net NntpNews Component -
Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine supports Post Alerts, Ratings, and Searching.
|||You shouldn't touch the distributor admin's password. To fix things you
really should disable publishing and reenable it.
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"SqlJunkies User" <User@.-NOSPAM-SqlJunkies.com> wrote in message
news:Or5756wiEHA.2448@.TK2MSFTNGP12.phx.gbl...
> DD,
> I am having the same problem here. It's stuck in the Snapshot Agent's
connecting attempt to the distributor. It's not even related to
Subscription. It just give up during initializing snapshot.
> The distributor_admin and sa password are set to the same and mapped in
remote_server login.
> The only thing I haven't tried is restart the MSSQL and SQLAgent because
all my clients are using the databases.
> --
> Posted using Wimdows.net NntpNews Component -
> Post Made from http://www.SqlJunkies.com/newsgroups Our newsgroup engine
supports Post Alerts, Ratings, and Searching.

Can't connect to databases through Enterprise Manager

Understand I am not a DBA. I am just the guy who has to
work with this stuff.
We have client software that uses SQL 7 as a database.
Winpak is a door access software made by Northern. It
stores proxy card info, access levels, historys, etc. in
a SQL 7 database. I know the databases are still there
because Winpak connects and I can pull up info.
This started because I noticed whoever set up the primary
and archive databases pointed them both to the same file
name. I backed up the primary and deleted it. Restored
it with the full backup and made sure it was pointed to a
different file name. Everything worked fine and still
showed up in Enterprise Manager. I restarted the computer
later and tried to go back into Enterprise Manager. Tried
to expand 'SQL Server Group' to list all the databases and
I got an error saying, "A connection could not be
established to COMPUTER - Cannot open user default
database '<ID>'. Using master database instead. Please
verify SQL Server is running and check your SQL Server
registration properties (by right-clicking on the COMPUTER
node) and try again."
My services were running just fine and when I checked my
registration properties everything looked fine. Redid the
registration properties with no luck. Using NT
authentication and even making a new one. The other
problem is that somebody set this thing up 3 years ago and
I have no idea what the 'sa' password is and I have tried
every simple password I can think of. I am checked out
the knowledge database articles matching my error message
and they didn't realy help cuz I either needed the 'sa'
password or I don't know how to impliment the solution
based on my limited knowledge of SQL. I need to do a
final backup to move all the info to a new machine with
SQL 2000. I am really stuck (and screwed) if I can't get
that info off cuz we just entered in a few hundred more
employees so using an old backup isn't going to save me.
Help would be greatly appreciated
Hi,
It seems the Login ID you are using is defaulted to the database you have
deleted. That is the reason you are getting the error.
How to change the SA Password,
1. Login to Query analyzer using Windows Authentication
2. Execute the beloe command
sp_password null,'passwordsa',sa
(now the password for sa is passwordsa)
How to change the default database of your existing users, which gave error
1. Login to query analyzer as SA
2. execute below statement
sp_defaultdb <loginame>,<new database name>
3. After this you will be able to login using the old id itself.
Thanks
Hari
MCDBA
"Brendan" <anonymous@.discussions.microsoft.com> wrote in message
news:124bf01c41152$811230e0$a501280a@.phx.gbl...
> Understand I am not a DBA. I am just the guy who has to
> work with this stuff.
> We have client software that uses SQL 7 as a database.
> Winpak is a door access software made by Northern. It
> stores proxy card info, access levels, historys, etc. in
> a SQL 7 database. I know the databases are still there
> because Winpak connects and I can pull up info.
> This started because I noticed whoever set up the primary
> and archive databases pointed them both to the same file
> name. I backed up the primary and deleted it. Restored
> it with the full backup and made sure it was pointed to a
> different file name. Everything worked fine and still
> showed up in Enterprise Manager. I restarted the computer
> later and tried to go back into Enterprise Manager. Tried
> to expand 'SQL Server Group' to list all the databases and
> I got an error saying, "A connection could not be
> established to COMPUTER - Cannot open user default
> database '<ID>'. Using master database instead. Please
> verify SQL Server is running and check your SQL Server
> registration properties (by right-clicking on the COMPUTER
> node) and try again."
> My services were running just fine and when I checked my
> registration properties everything looked fine. Redid the
> registration properties with no luck. Using NT
> authentication and even making a new one. The other
> problem is that somebody set this thing up 3 years ago and
> I have no idea what the 'sa' password is and I have tried
> every simple password I can think of. I am checked out
> the knowledge database articles matching my error message
> and they didn't realy help cuz I either needed the 'sa'
> password or I don't know how to impliment the solution
> based on my limited knowledge of SQL. I need to do a
> final backup to move all the info to a new machine with
> SQL 2000. I am really stuck (and screwed) if I can't get
> that info off cuz we just entered in a few hundred more
> employees so using an old backup isn't going to save me.
> Help would be greatly appreciated
|||Thanks for the post. It more or less led me to a
solution. I tried using NT authentication with no
success. Realized the machine was running on the admin
account with no password. For giggles I made a new admin
account with a different user name and an actual password
and tried again. Low and behold it worked. I got into
query analyzer and changed the sa password. Problem
solved. Thanks again.

>--Original Message--
>Hi,
>It seems the Login ID you are using is defaulted to the
database you have
>deleted. That is the reason you are getting the error.
>How to change the SA Password,
>1. Login to Query analyzer using Windows Authentication
>2. Execute the beloe command
> sp_password null,'passwordsa',sa
>(now the password for sa is passwordsa)
>How to change the default database of your existing
users, which gave error
>1. Login to query analyzer as SA
>2. execute below statement
> sp_defaultdb <loginame>,<new database name>
>3. After this you will be able to login using the old id
itself.
>Thanks
>Hari
>MCDBA
>
>
>"Brendan" <anonymous@.discussions.microsoft.com> wrote in
message
>news:124bf01c41152$811230e0$a501280a@.phx.gbl...
to
in
there
primary
file
Restored
to a
computer
Tried
and
Please
COMPUTER
my
the
and
tried
message
get
me.
>
>.
>

Can't connect to databases through Enterprise Manager

Understand I am not a DBA. I am just the guy who has to
work with this stuff.
We have client software that uses SQL 7 as a database.
Winpak is a door access software made by Northern. It
stores proxy card info, access levels, historys, etc. in
a SQL 7 database. I know the databases are still there
because Winpak connects and I can pull up info.
This started because I noticed whoever set up the primary
and archive databases pointed them both to the same file
name. I backed up the primary and deleted it. Restored
it with the full backup and made sure it was pointed to a
different file name. Everything worked fine and still
showed up in Enterprise Manager. I restarted the computer
later and tried to go back into Enterprise Manager. Tried
to expand 'SQL Server Group' to list all the databases and
I got an error saying, "A connection could not be
established to COMPUTER - Cannot open user default
database '<ID>'. Using master database instead. Please
verify SQL Server is running and check your SQL Server
registration properties (by right-clicking on the COMPUTER
node) and try again."
My services were running just fine and when I checked my
registration properties everything looked fine. Redid the
registration properties with no luck. Using NT
authentication and even making a new one. The other
problem is that somebody set this thing up 3 years ago and
I have no idea what the 'sa' password is and I have tried
every simple password I can think of. I am checked out
the knowledge database articles matching my error message
and they didn't realy help cuz I either needed the 'sa'
password or I don't know how to impliment the solution
based on my limited knowledge of SQL. I need to do a
final backup to move all the info to a new machine with
SQL 2000. I am really stuck (and screwed) if I can't get
that info off cuz we just entered in a few hundred more
employees so using an old backup isn't going to save me.
Help would be greatly appreciatedHi,
It seems the Login ID you are using is defaulted to the database you have
deleted. That is the reason you are getting the error.
How to change the SA Password,
1. Login to Query analyzer using Windows Authentication
2. Execute the beloe command
sp_password null,'passwordsa',sa
(now the password for sa is passwordsa)
How to change the default database of your existing users, which gave error
1. Login to query analyzer as SA
2. execute below statement
sp_defaultdb <loginame>,<new database name>
3. After this you will be able to login using the old id itself.
Thanks
Hari
MCDBA
"Brendan" <anonymous@.discussions.microsoft.com> wrote in message
news:124bf01c41152$811230e0$a501280a@.phx
.gbl...
> Understand I am not a DBA. I am just the guy who has to
> work with this stuff.
> We have client software that uses SQL 7 as a database.
> Winpak is a door access software made by Northern. It
> stores proxy card info, access levels, historys, etc. in
> a SQL 7 database. I know the databases are still there
> because Winpak connects and I can pull up info.
> This started because I noticed whoever set up the primary
> and archive databases pointed them both to the same file
> name. I backed up the primary and deleted it. Restored
> it with the full backup and made sure it was pointed to a
> different file name. Everything worked fine and still
> showed up in Enterprise Manager. I restarted the computer
> later and tried to go back into Enterprise Manager. Tried
> to expand 'SQL Server Group' to list all the databases and
> I got an error saying, "A connection could not be
> established to COMPUTER - Cannot open user default
> database '<ID>'. Using master database instead. Please
> verify SQL Server is running and check your SQL Server
> registration properties (by right-clicking on the COMPUTER
> node) and try again."
> My services were running just fine and when I checked my
> registration properties everything looked fine. Redid the
> registration properties with no luck. Using NT
> authentication and even making a new one. The other
> problem is that somebody set this thing up 3 years ago and
> I have no idea what the 'sa' password is and I have tried
> every simple password I can think of. I am checked out
> the knowledge database articles matching my error message
> and they didn't realy help cuz I either needed the 'sa'
> password or I don't know how to impliment the solution
> based on my limited knowledge of SQL. I need to do a
> final backup to move all the info to a new machine with
> SQL 2000. I am really stuck (and screwed) if I can't get
> that info off cuz we just entered in a few hundred more
> employees so using an old backup isn't going to save me.
> Help would be greatly appreciated|||Thanks for the post. It more or less led me to a
solution. I tried using NT authentication with no
success. Realized the machine was running on the admin
account with no password. For giggles I made a new admin
account with a different user name and an actual password
and tried again. Low and behold it worked. I got into
query analyzer and changed the sa password. Problem
solved. Thanks again.

>--Original Message--
>Hi,
>It seems the Login ID you are using is defaulted to the
database you have
>deleted. That is the reason you are getting the error.
>How to change the SA Password,
>1. Login to Query analyzer using Windows Authentication
>2. Execute the beloe command
> sp_password null,'passwordsa',sa
>(now the password for sa is passwordsa)
>How to change the default database of your existing
users, which gave error
>1. Login to query analyzer as SA
>2. execute below statement
> sp_defaultdb <loginame>,<new database name>
>3. After this you will be able to login using the old id
itself.
>Thanks
>Hari
>MCDBA
>
>
>"Brendan" <anonymous@.discussions.microsoft.com> wrote in
message
> news:124bf01c41152$811230e0$a501280a@.phx
.gbl...
to
in
there
primary
file
Restored
to a
computer
Tried
and
Please
COMPUTER
my
the
and
tried
message
get
me.
>
>.
>

Can't connect to Access project

I've given a copy of Access project to user (win2000prof) but not able to
connect to SQL server on remote server.
SQL driver in use on client is 3.70.09.61 - this gives error DBNMPNTM
specified SQL server not found.
On my PC ( XP and SQL driver 2000.85.1117.00 ) it connects with same login
details.
Can I just download updated version or do I need SQL client software
installed on PC?
Thanks
Try updating the MDAC version on the Windows 2000 client.
You can verify MDAC versions with the component checker. You
can download component checker and MDAC versions from:
http://msdn.microsoft.com/data/mdac/...s/default.aspx
-Sue
On Tue, 9 Aug 2005 07:21:04 -0700, lindab
<lindab@.discussions.microsoft.com> wrote:

>I've given a copy of Access project to user (win2000prof) but not able to
>connect to SQL server on remote server.
>SQL driver in use on client is 3.70.09.61 - this gives error DBNMPNTM
>specified SQL server not found.
>On my PC ( XP and SQL driver 2000.85.1117.00 ) it connects with same login
>details.
>Can I just download updated version or do I need SQL client software
>installed on PC?
>Thanks