sos 3.5.3 server

[Balwinder]

we are sos 3.5.3 server.earlier we have only 8 database projects in sos.we never face any problems,but when we have been blown up our database projects 8 to 23,after that we are facing problems.whenever i am trying to connect my sos server thru sos client its shows only 11 projects in database dropdown menu, we are able to conected 11 databased in sos client without any problem.
Is there any limitation of databases of sos server 3.5.3.
Please explain what is the problem and solution.
Thanks

[lbauer]

We've had users with 30 or more databases configured.

Check the SOS Server log.txt file in the SOS Server directory.

It may show infomation like "invalid database," or unable to open <path to database>.

Verify that the account used by the SOS Server Service has read\write access to all the directories where the VSS databases reside.

If the databases are not on the SOS Server machine, then use a domain account rather than the Local System account.

[bssalaria]

Hi ..thanx for suggestions..
We have one more problem in SOS 3.5.3 server.
SOS server machine has port 8888 open. This is required for SOS client. But when you do
telnet our firewall external IP address with port number 8888, it gives the following prompt. We need to make the
prompt blank ie. stop it from appearing.

200 Protocol-Version:2.0 Message-ID:00000000 Database
Aliases:Medimension,humana,schawkintegrated,Fujitsu,emr,imceda,advent,Mednet,blu
ebird,Schawkone,Proact Content-Length:318 E:\vss\Medimensions\srcsafe.ini
E:\vss\humana\srcsafe.ini E:\vss\schawkintegrated\srcsafe.ini
E:\vss\Fujitsu\srcsafe.ini E:\vss\emr\srcsafe.ini E:\vss\imceda\srcsafe.ini
E:\vss\advent\srcsafe.ini E:\vss\mednet\srcsafe.ini E:\vss\blue
bird\srcsafe.ini E:\vss\schawk1\srcsafe.ini E:\vss\Proact1\srcsafe.ini

Please look into the matter.what is the problem and solution.

Thanx.
Balwinder

[lbauer]

If this is a serious concern, you probably wouldn't want them posted in a public forum, either.

There's no way currently to prevent Telnet from showing the paths to the VSS databases. Although you can see the paths, we've never had reports of users being able to access the VSS database through SourceOffSite because of this information.

When used with encryption, SOS is very secure.

http://support.sourcegear.com/viewtopic.php?t=457

If someone can hack into your network and get into the databases then that's a security issue outside of SOS.

I will log this to our bug/feature database and we'll investigate the possibility of changing what's shown in Telnet.