Compaq P4, 512mb Ram, XPPro, Office 2002 Pro.
1. Before MS SQL 2000 Client install MS Access 2002 properly created a
new database in MYDOCUMENTS which is redirected to h:\users\%usern ame%
via Active Directory.
2. Upon installing SQl client, MS Access becomes non-responsive for about
3 minutes when clicking "Create New databse" and trying to change the
default filename from db1.mdb to anything else. As soon as you try
typing in the filename field, it freezes for 3 minutes and says NOT
RESPONDING. after 3 minites it comes back with the letter you hit in the
filename field. If you hit another letter, it freezes again. It only
freezes when you type in the filename field..then it freezes for 3
minutes, returns the character you typed, then freezes again when you try
to type another letter. If you do anything esle it works..after the
freeze returns, I can switch to a my C drive and it works fine.
If I were to switch from the networked MYDOCUMENTS to a location on my C:
drive and try it, it works fine, it does not freeze. It only happens
when you try to give a new database file a filename when pointing to a
networked drive location.
It opens exisiting files from the network location fine.
I tried uninstalling access, repairing, removing the SQL client, etc...
no luck... any ideas?
I checked the network config for the sql client... no named pipes, only
TCP is used and the alias is the servers IP.
MDAC Refresh release is also included in the Microsoft SQL Server 2000
Service Pack 3a release. I have applied SP3a to both the server and the
client.
XP is fully service packed, SQL is fully service packed, Office XP is
fully packed.
This one is a real head scratcher... its similar to the not responding
issues you used to see with name resolution... but I cannot think of how
that could be related to this.
My next step is to run a sniffer and see the traffic going on while it
names the file and freezes...
Im open to any other ideas at this point...
I uninstalled office completely, reinstalled, no luck
repaired with the cd, no luck
ran sfc, no luck
removed sql client, no luck.
XP SP1 was installed upon pc rollout. In fact all the recent critcal
updates are applied as well.
SQL SP 3 is applied SP3a.
I can create a DB locally, open it locally, manually copy it to the
network, open it, open exitising dbs off the network.
The only thing that causes this is when I select NEW DATABASE and try to
change the default filename when it is pointing to a net location. If I
change to local location first, then rename it, it works... if I stay on
a net location it locks for 3 mins.
PLease respond via email in addition to the group posting..I rarely check
the groups.
--
---------------
Mark M. Reed
mreed@reedassoc iates.com
1. Before MS SQL 2000 Client install MS Access 2002 properly created a
new database in MYDOCUMENTS which is redirected to h:\users\%usern ame%
via Active Directory.
2. Upon installing SQl client, MS Access becomes non-responsive for about
3 minutes when clicking "Create New databse" and trying to change the
default filename from db1.mdb to anything else. As soon as you try
typing in the filename field, it freezes for 3 minutes and says NOT
RESPONDING. after 3 minites it comes back with the letter you hit in the
filename field. If you hit another letter, it freezes again. It only
freezes when you type in the filename field..then it freezes for 3
minutes, returns the character you typed, then freezes again when you try
to type another letter. If you do anything esle it works..after the
freeze returns, I can switch to a my C drive and it works fine.
If I were to switch from the networked MYDOCUMENTS to a location on my C:
drive and try it, it works fine, it does not freeze. It only happens
when you try to give a new database file a filename when pointing to a
networked drive location.
It opens exisiting files from the network location fine.
I tried uninstalling access, repairing, removing the SQL client, etc...
no luck... any ideas?
I checked the network config for the sql client... no named pipes, only
TCP is used and the alias is the servers IP.
MDAC Refresh release is also included in the Microsoft SQL Server 2000
Service Pack 3a release. I have applied SP3a to both the server and the
client.
XP is fully service packed, SQL is fully service packed, Office XP is
fully packed.
This one is a real head scratcher... its similar to the not responding
issues you used to see with name resolution... but I cannot think of how
that could be related to this.
My next step is to run a sniffer and see the traffic going on while it
names the file and freezes...
Im open to any other ideas at this point...
I uninstalled office completely, reinstalled, no luck
repaired with the cd, no luck
ran sfc, no luck
removed sql client, no luck.
XP SP1 was installed upon pc rollout. In fact all the recent critcal
updates are applied as well.
SQL SP 3 is applied SP3a.
I can create a DB locally, open it locally, manually copy it to the
network, open it, open exitising dbs off the network.
The only thing that causes this is when I select NEW DATABASE and try to
change the default filename when it is pointing to a net location. If I
change to local location first, then rename it, it works... if I stay on
a net location it locks for 3 mins.
PLease respond via email in addition to the group posting..I rarely check
the groups.
--
---------------
Mark M. Reed
mreed@reedassoc iates.com