Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.
Any idea? Have i to reinstall 2000?
Tks,
LourivalAre both named instances or is one for them default instance and if so, whic
h is the default
instance? Is the SQL Server browser service started?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142254900.463560.180690@.e56g2000cwe.googlegroups.com...
> Hi,
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?
> Tks,
> Lourival
>|||one of then is the default instance, the 2000. The 2005 instance is
named.
tks,
Tibor|||So what error do you get when you run the following from a command prompt
osql -E -S (local)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>|||No error. It just became freezed. It=B4s the same for enterprise manager
or any app that try to connect.
regards,
Lourival|||OK, I thought it might be the SQL Browser service not started, but that shou
ld mean you can connect
to the default but not named. You seem to have the other way around. One mor
e thing you can check is
the netlib configuration. Except for that, I'm out of ideas, I'm afraid.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>sql

Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.
Any idea? Have i to reinstall 2000?
Tks,
LourivalAre both named instances or is one for them default instance and if so, which is the default
instance? Is the SQL Server browser service started?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142254900.463560.180690@.e56g2000cwe.googlegroups.com...
> Hi,
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?
> Tks,
> Lourival
>|||one of then is the default instance, the 2000. The 2005 instance is
named.
tks,
Tibor|||So what error do you get when you run the following from a command prompt
osql -E -S (local)
--
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>|||No error. It just became freezed. It=B4s the same for enterprise manager
or any app that try to connect.
regards,
Lourival|||OK, I thought it might be the SQL Browser service not started, but that should mean you can connect
to the default but not named. You seem to have the other way around. One more thing you can check is
the netlib configuration. Except for that, I'm out of ideas, I'm afraid.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegroups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>

Problems with SQL 2000 and 2005 on same machine - Can't connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.
Any idea? Have i to reinstall 2000?
Tks,
Lourival
Are both named instances or is one for them default instance and if so, which is the default
instance? Is the SQL Server browser service started?
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142254900.463560.180690@.e56g2000cwe.googlegr oups.com...
> Hi,
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?
> Tks,
> Lourival
>
|||one of then is the default instance, the 2000. The 2005 instance is
named.
tks,
Tibor
|||So what error do you get when you run the following from a command prompt
osql -E -S (local)
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegr oups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>
|||No error. It just became freezed. It=B4s the same for enterprise manager
or any app that try to connect.
regards,
Lourival
|||OK, I thought it might be the SQL Browser service not started, but that should mean you can connect
to the default but not named. You seem to have the other way around. One more thing you can check is
the netlib configuration. Except for that, I'm out of ideas, I'm afraid.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
<lourivalsjr@.gmail.com> wrote in message
news:1142270454.932906.302490@.j33g2000cwa.googlegr oups.com...
> one of then is the default instance, the 2000. The 2005 instance is
> named.
> tks,
> Tibor
>

Problems with SQL 2000 and 2005 on same machine - Cant connect on 2000

Hi,
i have SQL 2000 and 2005 on same machine(with different intance names,
of course), my laptop - XP with SP2. The 2005 works fine but i can't
connect on SQL 2000. All the the SQL services are started.

Any idea? Have i to reinstall 2000?

Tks,
Lourival(lourivalsjr@.gmail.com) writes:
> i have SQL 2000 and 2005 on same machine(with different intance names,
> of course), my laptop - XP with SP2. The 2005 works fine but i can't
> connect on SQL 2000. All the the SQL services are started.
> Any idea? Have i to reinstall 2000?

Exactly which service-pack level of SQL 2000 do you have? You can view
this on the first line of
C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG
(if this is the instance directory for SQL 2000.)

I believe you need at least SP3 (8.00.760 to run in parallel with SQL 2005.)

Another thing to try is to open the Server and Client Network Utilities of
SQL 2000, and make sure that both use TCP/IP. For local connections,
shared memory is the default, but if it for some reason does not work, you
can try TCP/IP.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Problems with New Sql Server registration

HI,
I have SQL Server 2000 Evaluation running on Win 2k Pro, and i'm trying to register/connect to my webhost's Sql Server through my Enterprise Manager.

I followed the exact instructions that my webhost sent to me as follows:
1) open the Client Network Utility which comes with SQL 2000
2) Make sure that the default network library is set to TCP/IP on
the general tab
3) add a server alias by clicking add
4) type in xxx.xxx.xxx.xx then click ok and apply the changes

Next you need to add our SQL server in Enterprise Manager:
1) right click on SQL Server Group
2) Click New SQL Server Registration
3) choose to use the wizard your first time doing this and click next
4) in available servers, type in xxx.xxx.xxx.xxx and click add and
next
5) Click the SQL server login from the connection options
6) Enter the username and password you were given/requested
7) Click add the SQL server to an existing server group and choose
one
8) Click finish

I keep getting the error "SQL Server does not exist or access denied."
my web host says the problems seems to be with what I'm doing , as we've tried 2 separate IP address's and it seems to run fine on their end.

Is there anything i can do to trouble shoot this ?
I'm at a complete loss now.

Thanks for any help!!I'm a little puzzled by the instruction to add a server alias. My understanding was that a server alias was to allow you to convert a name to an IP address (a mini DNS lookup on your PC). Why you would have to enter the IP address into the server alias screen and then re-enter the IP address in the connection screen is a bit perplexing to me.

Some things to check:
1. Can you ping the designated IP address?
2. Are you attempting to access the web host SQL server from behind a firewall? If so, is port 1433 open to traffic (and if so, why!?!?)?
3. I have also found that putting an entry in the LMHOST file under WINNT\SYSTEM32\DRIVERS\ETC will work. If you've never played with it, though I would not necessarily recommend this as option one.

Hope this helps.

Hugh Scott

Originally posted by dougwood
HI,
I have SQL Server 2000 Evaluation running on Win 2k Pro, and i'm trying to register/connect to my webhost's Sql Server through my Enterprise Manager.

I followed the exact instructions that my webhost sent to me as follows:
1) open the Client Network Utility which comes with SQL 2000
2) Make sure that the default network library is set to TCP/IP on
the general tab
3) add a server alias by clicking add
4) type in xxx.xxx.xxx.xx then click ok and apply the changes

Next you need to add our SQL server in Enterprise Manager:
1) right click on SQL Server Group
2) Click New SQL Server Registration
3) choose to use the wizard your first time doing this and click next
4) in available servers, type in xxx.xxx.xxx.xxx and click add and
next
5) Click the SQL server login from the connection options
6) Enter the username and password you were given/requested
7) Click add the SQL server to an existing server group and choose
one
8) Click finish

I keep getting the error "SQL Server does not exist or access denied."
my web host says the problems seems to be with what I'm doing , as we've tried 2 separate IP address's and it seems to run fine on their end.

Is there anything i can do to trouble shoot this ?
I'm at a complete loss now.

Thanks for any help!!|||thanks hmscott,
well I pinged the address successfully. I don;t know much about firewalls so does that mean that I am not hindered by any firewall, or does that just tell me that the host address is valid ?

i'm beginning to think that they are giving me the wrong username and password or something.
Don't ever use setupsite.com. I've had nothing but problems with them !!

I haven't tried your last suggestion but It looks scary!!|||That you are able to ping the site successfully simply means that it is a valid IP address; it does not mean anything about a firewall.

I doubt very much that it is a userid/password issue. Your SQL clients can't "see" the SQL Service that is running on the destination IP. That can mean either that the SQL Service is not running on that IP, or that you are prevented from seeing the SQL Service because port 1433 is being blocked. How are you connecting to the network (internet connection via dial-up ISP? internet via DLS/cable? internet through a company-owned network?)? If it is the latter case, then you are likely contending with a firewall issue.

There are some tools that you can download from the internet to help:

1. SQL Ping (helps locate SQL server)
2. WhatsRunning (sp?) (helps determine all valid services running on an IP)

There are probably some others that I am overlooking.

Try removing the alias entry in your SQL Network set up. Then try connecting using SQL Query Analyzer and use the plain IP Address. If that does not work, then I'm sort of out of options -- my knowledge once you get down to the network level is woefully inadequate.

Regards,

Hugh Scott

PS. The LMHOST option isn't scary, but it is very much hidden from view and it's easy to forget that you have made the entries. Then it can become difficult to diagnose/troubleshoot problems that come up later.

Originally posted by dougwood
thanks hmscott,
well I pinged the address successfully. I don;t know much about firewalls so does that mean that I am not hindered by any firewall, or does that just tell me that the host address is valid ?

i'm beginning to think that they are giving me the wrong username and password or something.
Don't ever use setupsite.com. I've had nothing but problems with them !!

I haven't tried your last suggestion but It looks scary!!|||hmscott,
thanks so much. for some weird ass reason, I got it to work after I deleted the Alias from Client Network Utility ?!!!
sort of bizarre huh?
I just went directly to Enterprise Manager, right clicked on my SQL Server group and New SQL Server Registration, typed in the IP and went through the rest of the Wizard and it worked fine.

thanks so much for your time, you saved me many hours of pulling my hair out and waiting for my lame webhost to get in touch with me!!
cheers.|||Glad to help...

Originally posted by dougwood
hmscott,
thanks so much. for some weird ass reason, I got it to work after I deleted the Alias from Client Network Utility ?!!!
sort of bizarre huh?
I just went directly to Enterprise Manager, right clicked on my SQL Server group and New SQL Server Registration, typed in the IP and went through the rest of the Wizard and it worked fine.

thanks so much for your time, you saved me many hours of pulling my hair out and waiting for my lame webhost to get in touch with me!!
cheers.

Problems with MSDE

Hi all

I'v got a Windows XP Pro SP1 Box with MSDE sql2k SP3. The installation
was not the problem, but if i would connect with a client like dbamgr2k
or the MS Enterprise client, the client hangs up. If i try a nonlocal
server, it hangs too. What's the problem?

Markushi Markus,
"Markus Graf" <gurix@.bluewin.ch> ha scritto nel messaggio
news:2uejnbF28p144U1@.uni-berlin.de
> Hi all
> I'v got a Windows XP Pro SP1 Box with MSDE sql2k SP3. The installation
> was not the problem, but if i would connect with a client like
> dbamgr2k or the MS Enterprise client, the client hangs up. If i try a
> nonlocal server, it hangs too. What's the problem?
> Markus

MSDE installs by default disabling the network protocols, thus only local
connections are enabled... in order to allow remote connections, you have to
re-enable them, running the Server Network Utility (svrnetcn.exe)... restart
the service...
to enable network protocols at install time, you have to provide the
DISABLENETWORKPROTOCOLS=0
parameter to the setup.exe bootstrap installer of MSDE

on WinNT platforms MSDE installs by default allowing only truste
connections, thus SQL Server authenticated connections (providing Username
and Password) are not allowed.. in order t change this behaviour, you have
to modify the Windows registry as explained in
http://support.microsoft.com/defaul...kb;en-us;285097
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
--- remove DMO to reply

Problems with login

I have a few proggramers in my firm. They connect to server with login 'prog' (not 'sa'). I don't want to give them sysadmin rights, because I don't want to allow them to CREATE, ALTER, DROP, DETACH, ATACH, BACKUP, RESTORE ... DATABASE, and some other things (sp_addlogin, sp_password, ...).
They have db_owner role for one of few database we have, with all permissions on the objects of that database. But, they can not use SQL-Profiler wich is a poweful for them to manage theirs applications, because they are not member of sysadmin role.
How can I avoid that.
Can I give them sysadmin rights, but to exclude some privileges.
Or, what to add, to be able to use SQL Profiler, without sysadmin rights

Thanks for any helpYou can create a proxy account for your developer

1. Open Enterprise manager.
2. Click on the server name -> Management
3. Right Click on SQL Server Agent
4. Choose the Job System tab
5. Uncheck the box that says "Only users with sysadmin privleges can execute CMdExec and ActiveScripting job steps.
6. You will be prompted to enter log in information - enter the system account info you want to use (Domain or Local) to run scripts - it should be at least a local admin account for the box, I normally use the same logon as that used by the MSSQL service.

Verify/Change permissions

1. Open Administrative tools (You will need admin rights on the server to do this)
2. Go to Local Security Policy (this can also be done at the domain level, speak to your LAN admin about how they would like this setup)
3. Click on "user rights Assignment" in the left hand pane.
4. In the right hand pane, scroll down until you find "replace a process level token".
5. Double click on "Replace a Process level token", and add the proxy user account (Step 6 above).
6. Apply the change. You may have to restart the MSSQL and SQL Server Agent services for the change to take place, I am not sure.

And since your developers are not in the sysadmin group you as the person that is located in the sysadmin group will need to create the proxy account.

You may need to investiagate what rights you can give to the proxy account.

I hope this is helpful.

Lystra

Problems with KV 934458

I attempted to install KB 934458 today, but the installation failed. Now, when I try to connect to my SQL server, I fail and get Microsoft SQL Server Error: 2. This error was not occurring until I attempted to install the today's hotfix (934458).

Anyone know of a workaround?

Workaround: If you don't have the issues that Update resolves, simply reboot and hide the update.

Details: I had the exact same issue. That update has tried to install itself 4 times on my machine - all unsuccessfullly. If I simply rebooted, I could access my server again. Here's the issues this is supposed to resolve:

Critical Update for SQL Server 2005 Service Pack 2 (KB 934458)

Download size: 18.2 MB

You may need to restart your computer for this update to take effect.

Update type: Important

The initial release of SQL Server 2005 Service Pack 2 (SP2) contained an issue that caused maintenance plan cleanup tasks to remove data before the specified cleanup interval. Install this update to correct the interpretation of existing cleanup task intervals, and to avoid this issue in new cleanup tasks. After you install this item, you may have to restart your computer.

More information:
http://support.microsoft.com/kb/934458

I don't have issues there, so I'll skip that update until it's fixed.

(I suspect you've already done this. I hope someone will post here if the update starts working.)|||On my machine it's even worse: I'm getting a BSOD every time I try to launch SQL Server tools, re-install SP2, the patch 934458, or uninstall any of that.

The whole installation is completely blocked and unusable now, and cannot even be uninstalled -- not even after I clean all SQL Server-related install entries using MS Installer Cleanup utility and try to re-apply SP2. BSOD after BSOD after BSOD.

The patch 934458 is the direct cause of the whole mess.

[EDIT]

There seem to be two different patches for the same issue:

http://www.sqlservercentral.com/columnists/sjones/2958_printversion.asp

I have installed my SQL Server and automatically applied SP2, and then had Windows Update telling me I should install 934458.

I guess I should have ignored that and installed the other one, 934459 (90+ MB), which is what I'm about to do right now (fingers crossed).

|||I had a heck of a hard time installing this hotfix, but finally discovered that the Hotfix updater was trying to make a temporary copy of the patch (and failing) to my F: drive, which is a virtual drive I have which maps to a subdirectory on my C: drive. I don't know why the Hotfix was choosing to go there instead of my typical default C: drive, but I was able to succeed in getting the install to work by temporarily removing my F: drive (via "subst /d f:" at a command prompt) and then rerunning the manual install.

This is clearly a bug in the Hotfix. Again, I was able to get the install to work just by unmapping my virtual drives.
|||Well my MSSQLServer will now not start after a reboot! Great fun. I downloaded 934458 and tired again after the windows update failure. It install success on all but database services. So until I find a fix my MSSQL is offline. Anyone have a suggestion?

Problems with KB 934458

I attempted to install KB 934458 today, but the installation failed. Now, when I try to connect to my SQL server, I fail and get Microsoft SQL Server Error: 2. This error was not occurring until I attempted to install the today's hotfix (934458).

Anyone know of a workaround?

Workaround: If you don't have the issues that Update resolves, simply reboot and hide the update.

Details: I had the exact same issue. That update has tried to install itself 4 times on my machine - all unsuccessfullly. If I simply rebooted, I could access my server again. Here's the issues this is supposed to resolve:

Critical Update for SQL Server 2005 Service Pack 2 (KB 934458)

Download size: 18.2 MB

You may need to restart your computer for this update to take effect.

Update type: Important

The initial release of SQL Server 2005 Service Pack 2 (SP2) contained an issue that caused maintenance plan cleanup tasks to remove data before the specified cleanup interval. Install this update to correct the interpretation of existing cleanup task intervals, and to avoid this issue in new cleanup tasks. After you install this item, you may have to restart your computer.

More information:
http://support.microsoft.com/kb/934458

I don't have issues there, so I'll skip that update until it's fixed.

(I suspect you've already done this. I hope someone will post here if the update starts working.)|||On my machine it's even worse: I'm getting a BSOD every time I try to launch SQL Server tools, re-install SP2, the patch 934458, or uninstall any of that.

The whole installation is completely blocked and unusable now, and cannot even be uninstalled -- not even after I clean all SQL Server-related install entries using MS Installer Cleanup utility and try to re-apply SP2. BSOD after BSOD after BSOD.

The patch 934458 is the direct cause of the whole mess.

[EDIT]

There seem to be two different patches for the same issue:

http://www.sqlservercentral.com/columnists/sjones/2958_printversion.asp

I have installed my SQL Server and automatically applied SP2, and then had Windows Update telling me I should install 934458.

I guess I should have ignored that and installed the other one, 934459 (90+ MB), which is what I'm about to do right now (fingers crossed).

|||I had a heck of a hard time installing this hotfix, but finally discovered that the Hotfix updater was trying to make a temporary copy of the patch (and failing) to my F: drive, which is a virtual drive I have which maps to a subdirectory on my C: drive. I don't know why the Hotfix was choosing to go there instead of my typical default C: drive, but I was able to succeed in getting the install to work by temporarily removing my F: drive (via "subst /d f:" at a command prompt) and then rerunning the manual install.

This is clearly a bug in the Hotfix. Again, I was able to get the install to work just by unmapping my virtual drives.
|||Well my MSSQLServer will now not start after a reboot! Great fun. I downloaded 934458 and tired again after the windows update failure. It install success on all but database services. So until I find a fix my MSSQL is offline. Anyone have a suggestion?

Problems with a JET-ODBC-Connection and Access97-Runtime

I have a very strange problem with a JET-ODBC-Connection.
Using Access97-Runtime, we connect the table with a
DSN-less-ODBC-Connection to SQLServer 2000 SP3.
The Application runs on a Windows Server 2003 Terminal-Server with
CITRIX Metaframe.
Office 2003 is also installed (no Access2003)
And now the problem:
When our application is installed anew, the ODBC-Connection works fine.
When I start any Office2003-Application like Winword, the system files
MSJINT35.DLL and MSJTER35.DLL are changed. (I used ashampoo Uninstaller
Suite to check this issue).
Afterwards, our Application doesn't run anymore, the Application quits
without any error.
If I copy the MSJINT35.DLL anew from the install-directory, our
application runs again correctly.
The strange thing is, that the "changed" MSJINT35.DLL is exactly the
same as the original file. Version, Metadata, Language, Filesize, and
even a Hex-based-compare result that the files are identically.
Nevertheless, a copy of the file into system32 is a workaround to fix
the problem for a few hours.
Does anyone has any idea? PLEASE HELP!
How are you installing the app? I use Wise Install Builder, which installs
the Access 97 runtime into it's own folder - C:\Program Files\Access 97
Runtime. It installs the DLLs in question into that folder, too. The reason
being - when an app looks for DLL's it starts with the folder the app
started in, then looks in the folders in the PATH environment variable (e.g.
System32). You could probably solve your problem by having your installer
put the DLLs in question into the Runtime folder.
"Andreas Lauffer" <alweb01@.online.de> wrote in message
news:1132133394.166634.268470@.z14g2000cwz.googlegr oups.com...
> I have a very strange problem with a JET-ODBC-Connection.
> Using Access97-Runtime, we connect the table with a
> DSN-less-ODBC-Connection to SQLServer 2000 SP3.
> The Application runs on a Windows Server 2003 Terminal-Server with
> CITRIX Metaframe.
> Office 2003 is also installed (no Access2003)
> And now the problem:
> ----
> When our application is installed anew, the ODBC-Connection works fine.
> When I start any Office2003-Application like Winword, the system files
> MSJINT35.DLL and MSJTER35.DLL are changed. (I used ashampoo Uninstaller
> Suite to check this issue).
> Afterwards, our Application doesn't run anymore, the Application quits
> without any error.
> If I copy the MSJINT35.DLL anew from the install-directory, our
> application runs again correctly.
> The strange thing is, that the "changed" MSJINT35.DLL is exactly the
> same as the original file. Version, Metadata, Language, Filesize, and
> even a Hex-based-compare result that the files are identically.
> Nevertheless, a copy of the file into system32 is a workaround to fix
> the problem for a few hours.
> ----
> Does anyone has any idea? PLEASE HELP!
>

Problems with a JET-ODBC-Connection and Access97-Runtime

I have a very strange problem with a JET-ODBC-Connection.
Using Access97-Runtime, we connect the table with a
DSN-less-ODBC-Connection to SQLServer 2000 SP3.
The Application runs on a Windows Server 2003 Terminal-Server with
CITRIX Metaframe.
Office 2003 is also installed (no Access2003)
And now the problem:
----
When our application is installed anew, the ODBC-Connection works fine.
When I start any Office2003-Application like Winword, the system files
MSJINT35.DLL and MSJTER35.DLL are changed. (I used ashampoo Uninstaller
Suite to check this issue).
Afterwards, our Application doesn't run anymore, the Application quits
without any error.
If I copy the MSJINT35.DLL anew from the install-directory, our
application runs again correctly.
The strange thing is, that the "changed" MSJINT35.DLL is exactly the
same as the original file. Version, Metadata, Language, Filesize, and
even a Hex-based-compare result that the files are identically.
Nevertheless, a copy of the file into system32 is a workaround to fix
the problem for a few hours.
----
Does anyone has any idea? PLEASE HELP!How are you installing the app? I use Wise Install Builder, which installs
the Access 97 runtime into it's own folder - C:\Program Files\Access 97
Runtime. It installs the DLLs in question into that folder, too. The reason
being - when an app looks for DLL's it starts with the folder the app
started in, then looks in the folders in the PATH environment variable (e.g.
System32). You could probably solve your problem by having your installer
put the DLLs in question into the Runtime folder.
"Andreas Lauffer" <alweb01@.online.de> wrote in message
news:1132133394.166634.268470@.z14g2000cwz.googlegroups.com...
> I have a very strange problem with a JET-ODBC-Connection.
> Using Access97-Runtime, we connect the table with a
> DSN-less-ODBC-Connection to SQLServer 2000 SP3.
> The Application runs on a Windows Server 2003 Terminal-Server with
> CITRIX Metaframe.
> Office 2003 is also installed (no Access2003)
> And now the problem:
> ----
> When our application is installed anew, the ODBC-Connection works fine.
> When I start any Office2003-Application like Winword, the system files
> MSJINT35.DLL and MSJTER35.DLL are changed. (I used ashampoo Uninstaller
> Suite to check this issue).
> Afterwards, our Application doesn't run anymore, the Application quits
> without any error.
> If I copy the MSJINT35.DLL anew from the install-directory, our
> application runs again correctly.
> The strange thing is, that the "changed" MSJINT35.DLL is exactly the
> same as the original file. Version, Metadata, Language, Filesize, and
> even a Hex-based-compare result that the files are identically.
> Nevertheless, a copy of the file into system32 is a workaround to fix
> the problem for a few hours.
> ----
> Does anyone has any idea? PLEASE HELP!
>

Problems when Oracle running on same machine

I was deploying my Report Model in Visual Studio but got an error that it couldnt connect to my Report Server while it was running.

When i typed the address of my ReportServer I got an error, then when I typed the name of the localhost got an Oracle screen. So then I decided to turn off all the Oracle things running on the machine. Then when I tried to deploy again it worked and I could go to my ReportServer without problems.

I assume you aren't trying to build a Report Model on top of Oracle, it just happens to be running. The only thing I can think is that Oracle is taking over the HTTP port configured for Reporting Services.|||I think this is the reason as well, I just wanted to point this out to other users that they should look at this when they cannot connect to their ReportServer when Oracle is running. Is there a way that I can give preference to Microsoft instead of Oracle ?|||I'm not very familiar with Oracle's HTTP stack. You don't mention which version of Oracle you are using but 10g comes with a modified version of Apache called OHS. I think there are configurations where you can tell it to listen on a port not managed by IIS.|||<a href= http://voip-forum.tmcnet.com/forum/forum_posts.asp?TID=55428&PN=1&TPN=1 >Enter here</a>

problems when connecting with server

Hi, I am developing an application in where I connect with my server of SQL,

but at the time of making pull this offer one exepcion,

the code that I use is the following one

Dim rda As SqlCeRemoteDataAccess = Nothing

rda = New SqlCeRemoteDataAccess

rda.InternetUrl = "http://my-computer/SQLCE/sscesa20.dll"

rda.LocalConnectionString = "Data Source = C:\BD\rda_lab.SDF"

rda.Pull("authors", "SELECT * FROM Authors", "Provider = SQLOLEDB.1; Data Source = my-server; User ID = sa; PASSWORD = psw; initial catalog = SQLCE", RdaTrackOption.TrackingOn)

rda.Dispose()

The message that shows is:

Unhandled Execution Error

Line 40: rda.Pull("authors", "SELECT * FROM Authors..............

I have proven many things and I have not been able to solve I hope it and somebody can help me

So you're using SQL CE 2.0 (from InternetUrl property) which is not supported on desktop and yet providing path to the SDF file which is only valid on desktop (as it has drive letter). That seems to be wrong…

|||Hi Ilya Tumanov , perhaps it does not explain to me correctly.I am developing to an application Web where desire to take the data from my DataBase and to show them in a List Box, when executing the instruction pull before gives back the mentioned error to me|||

What I'm saying is: your RDA code is definitely wrong, it does not matter what exactly you're planning to do with data.

Your InternetUrl and LocalConnectionString properties are in conflict, they can't both be correct.

Problems when connect sql2005 locally

Hi All,

When I use asp.net 1.1 to connect sql 2005 enterprise server which just enable local access option instead of remote, I got error message to say database server is not avaiable. I use following connection string

user id=abc;password=abc;server=(local);Integrated Security = SSIP;

user id=abc;password=abc;server=.;Integrated Security = SSIP;

Actually, I used default instance, and ASP.Net and database server are in same server. Everything is fine when I change connection string as

user id=abc;password=abc;server=servername;Integrated Security = SSIP;

Frank,

This is a known issue when SS25 does not have TCP on, the client is using MDAC/Everret(.Net1.1) OLEDB provider. For connection sting like (local) or “.”, the connection will fail.

One of the workaround, if TCP/IP is off, is to use hostname in connection string that will connect you through named pipe provider, which is what you have seen.

Thanks,

|||

One more note is that if you can't change the your applications and they use "(local)" and "." in connection string, you can create aliases for "(local)", and "." using tools like cliconfg.exe or SQL Server Configuration Manager.

Please also not that the the there is a typo in your connection string, it should be "SSPI" instead of "SSIP".