SoS processor hits 100% after 24 -48 hours

If you are having a problem using SourceOffSite, post a message here.

Moderator: SourceGear

Post Reply
Randyh
Posts: 3
Joined: Mon Jul 12, 2004 9:54 am

SoS processor hits 100% after 24 -48 hours

Post by Randyh » Wed Jul 21, 2004 10:49 am

See attached text file for example and more information.
Attachments
SoSerrors.txt
(7.31 KiB) Downloaded 624 times

Guest

Post by Guest » Wed Jul 21, 2004 12:56 pm

It seems to be doing it more often then 24 hours now. I restarted the service around 6am and it went crazy again around 2:15pm.

7/21/2004 2:16:28 PM - 5: Invalid OLEVERB structure (80040000)
7/21/2004 2:16:28 PM - 5: Invalid OLEVERB structure (80040000)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/Weapon" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/UpdateIndex" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/Tspi" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/Time" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/Sensor" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/Platform" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/Orientation" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/Interaction" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/GatewayBase" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/EntityType" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/Entity" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax: "$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr/Cartesian" (8004d6ed)
7/21/2004 2:16:30 PM - 5: An item with the name $/Development/Implementation/GW/Msr/Application already exists (8004d694)
7/21/2004 2:16:30 PM - 5: An item with the name $/Development/Implementation/GW/Msr/bin already exists (8004d694)
7/21/2004 2:16:30 PM - 5: An item with the name $/Development/Implementation/GW/Msr/GWFramework already exists (8004d694)
7/21/2004 2:16:30 PM - 5: An item with the name $/Development/Implementation/GW/Msr/include already exists (8004d694)
7/21/2004 2:16:31 PM - 5: An item with the name $/Development/Implementation/GW/Msr/Application/Conversion already exists (8004d694)
7/21/2004 2:16:31 PM - 5: An item with the name $/Development/Implementation/GW/Msr/Application/impls already exists (8004d694)
7/21/2004 2:16:31 PM - 5: An item with the name $/Development/Implementation/GW/Msr/Application/lib already exists (8004d694)
7/21/2004 2:16:31 PM - 5: An item with the name $/Development/Implementation/GW/Msr/Application/LROM_NTMFv0_1 already exists (8004d694)
7/21/2004 2:16:31 PM - 5: An item with the name $/Development/Implementation/GW/Msr/Application/impls/Msr already exists (8004d694)
7/21/2004 2:16:31 PM - 5: An item with the name $/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd already exists (8004d694)
7/21/2004 2:16:31 PM - 5: An item with the name $/Development/Implementation/GW/Msr/Application/impls/Msr/main already exists (8004d694)
7/21/2004 2:16:31 PM - 5: An item with the name $/Development/Implementation/GW/Msr/Application/impls/Msr/Msr already exists (8004d694)

Guest

Post by Guest » Wed Jul 21, 2004 6:00 pm

Well now I'm confused. Its happening all the time now. This time no "real" errors in the logs. I monitored the processor this time and the first user connects, no problems. Once the second user connected it shot straight to 100%.

Based on the log I'm unsure if its something the client is doing or the second connection. Redardless it was not doing this before.

7/21/2004 7:39:31 PM - Started at 7/21/2004 7:39:31 PM

7/21/2004 7:39:31 PM - General logging level is Error. Method logging is Disabled.

7/21/2004 7:39:31 PM - Number of licenses configured: 22
7/21/2004 7:39:31 PM - SourceSafe Initialization file(s) located at:
7/21/2004 7:39:31 PM - C:\Simultation01\IBC Visualization\Phase I\Document CM\CM DB (VSS only)\srcsafe.ini
7/21/2004 7:39:31 PM - C:\Simultation01\Joust\Phase I\JOUST'03\ADMIN - MANAGEMENT\Document CM\CM Database\srcsafe.ini
7/21/2004 7:39:31 PM - C:\Simultation01\Joust\Phase 2\Document CM\CM DB(VSS only)\srcsafe.ini
7/21/2004 7:39:31 PM - C:\Simultation01\MSR\PhaseIII\Document CM\CM DB (VSS only)\srcsafe.ini
7/21/2004 7:39:31 PM - C:\Simultation01\OFW\PHASE II\Document CM\CM DB (VSS only)\srcsafe.ini

7/21/2004 7:39:31 PM - LCDATA is attempting to listen for connections on secure port 8890
7/21/2004 7:39:31 PM - LCDATA is attempting to listen for connections on unsecure port 8888

7/21/2004 7:39:31 PM - Waiting for a connection....secure = False
7/21/2004 7:39:31 PM - Waiting for a connection....secure = True

7/21/2004 7:40:52 PM - Connection accepted from 198.151.12.15:62109 on local address 192.168.10.252:8890, session id is 1.
7/21/2004 7:41:31 PM - 1: An item with the name $/Development Archive/Gateway 2003 (FY02)/iNet-HLA/VT/MsrGateway already exists (8004d694)
7/21/2004 7:41:31 PM - 1: An item with the name $/Development Archive/Gateway 2003 (FY02)/iNet-HLA/VT/MsrGateway/Makefile already exists (8004d694)
7/21/2004 7:41:31 PM - 1: An item with the name $/Development Archive/Gateway 2003 (FY02)/iNet-HLA/VT/MsrGateway/bin already exists (8004d694)
7/21/2004 7:41:32 PM - 1: An item with the name $/Development Archive/Gateway 2003 (FY02)/iNet-HLA/VT/MsrGateway/bin/em already exists (8004d694)
7/21/2004 7:41:32 PM - 1: An item with the name $/Development Archive/Gateway 2003 (FY02)/iNet-HLA/VT/MsrGateway/bin/nns already exists (8004d694)
7/21/2004 7:41:32 PM - 1: An item with the name $/Development Archive/Gateway 2003 (FY02)/iNet-HLA/VT/MsrGateway/Docs already exists (8004d694)
7/21/2004 7:41:32 PM - 1: An item with the name $/Development Archive/Gateway 2003 (FY02)/iNet-HLA/VT/MsrGateway/Docs/Design already exists (8004d694)
7/21/2004 7:41:46 PM - 1: An item with the name $/Development Archive/Gateway 2003 (FY02)/iNet-HLA/VT/MsrGateway/Docs/Design/AssumptionsforiNet-RTIGateway.doc already exists (8004d694)
7/21/2004 7:41:50 PM - 1: An item with the name $/Development Archive/Gateway 2003 (FY02)/iNet-HLA/VT/MsrGateway/Docs/Design/GRIM_RPR-FOM_1-0v3.doc already exists (8004d694)
7/21/2004 7:46:15 PM - Connection accepted from 198.151.12.15:44605 on local address 192.168.10.252:8890, session id is 2.

*** shot to 100% about this time ***

Randy_H

Post by Randy_H » Thu Jul 22, 2004 10:23 am

OK I verifed its has nothing to do with more than one connection. I verifed this by connectiing two users externally from behind the same firewall (NATing to the same IP). I'm "guessing" its something the client is doing.

I can email the full Log file. just need an address.

Help, Anyone?? My boss is about to drop the whole SoS product.

RandyH
(randy@sito.saic.com)

Windows 2000 SP4 , SoS 4.0.2, 22 users

lbauer
Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear

Post by lbauer » Sat Jul 24, 2004 9:14 pm

Did this happen right after you upgraded?

Your log file shows:

"$/Development/Implementation/GW/Msr/Application/impls/Msr/.dpnd/Msr" (8004d6ed)
7/21/2004 2:16:28 PM - 5: Invalid SourceSafe syntax:

We had another report from a user who was having problems with file or folder names that started with a period or dot like in ".dpnd."

We just got the other report so we still are doing some testing. I got the same error message with VSS, so we need to determine if the VSS version makes a difference.

What version of VSS are you using?

If SOS 4.02 is currently unusable, can you go back to 3.5.3 temporarily until we determine a fix or workaround? You can install both on the same machine. You still should have your 3.5.x serial numbers.

You can email your log to linda@sourcegear.com
Linda Bauer
SourceGear
Technical Support Manager

Guest

Post by Guest » Mon Jul 26, 2004 10:16 am

-We are currently using VSS 6.0 (build 8163)

-The problem started about a week after upgrading to 4.0.2. Not right away.

- I upped our logging to informational to see if its a single user causing this. I will monitor this tonight (connection from Hawaii) If nothing looks out of place and the processor hits 100% I will email you the log file.

Randy

- We have purchased 12 new licenses since the upgrade so we are unable to revert back to 3.5.3

Post Reply