Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Visual Studio.NET / Source Safe / December 2003

Tip: Looking for answers? Try searching our database.

Performance problem with VSS over NetWare

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
anonymous@discussions.microsoft.com - 23 Dec 2003 09:41 GMT
Hi all,
We're trying to use VSS with PowerBuilder 9. We managed to
create a working environment that seems to work correctly,
though we have some serious performance issues.
First, I must say I'm positive the problems are not with
VSS itself, but rather in the environment configuration.
Having that said, the most important detail is that we use
a Novell NetWare network rather than Microsoft's. We do
connect to our file server through the MS path
(\\server\... rather than T:\...), but our system guy told
me this would definitely make work slower.
I was wondering if anyone here has some experience with
using VSS (6) over a Netware network, or a possible
workaround to offer (given that the company uses NetWare,
and only the developers use VSS).
TIA,
Eran

BTW, is there a reason the word "netware" cannot be found
in any of the newsgroups? Am I the first one to come
across a problem that involves the use of a Microsoft tool
in a Novell environment?
anonymous@discussions.microsoft.com - 24 Dec 2003 12:36 GMT
I've found a surprising (partial) solution:
When selecting a VSS database, even if we chose the
srcsafe.ini file through the novell path (T:\...), it
would be translated to an NT path (\\server\...). BTW, the
translation was erroneous, so eventually we had to select
the file via "network places".
The workaround is simple: I've modified the registry entry
to the right novell path. Turns out VSS has no problem
working with a novell path - it's just impossible to
define one in a straightforward manner.
I'm neither a VSS nor a NetWare expert, but this looks to
me like one hell of a bug in VSS. Is there any MS person
around who'd like to comment on that?

Eran

>-----Original Message-----
>Hi all,
[quoted text clipped - 20 lines]
>in a Novell environment?
>.

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.