dotSoftwaredotDevelopmentdotCustomersdotAbout us
PushOk logoblank
bullet Home
bullet My software
bullet Support
bullet My payments
bullet My info
bullet Subscriptions
bullet Voting
bullet Contact us
fast linksFast Links
news&eventsnews and events

2012-12-21 
Major update of SVN SCC plug-in - versions 1.7.2 are finaly released

2012-12-21 
Major update of SVNCOM version 1.7.2 are finaly released

Lightweight embedded Node.js database with MongoDB API.

Ticket

Search go
PushOk Logo blank
leftTicketright

'Unspecified Error' from VS.NET SCC integration

( CVSSCC )
Type: Public Status:Closed Created: 14 May 04 05:00 Updated: 17 May 04 05:00
--> Igor Pushkov (admin)  at 17 May 04 05:00 writes

I am sorry for delay with answer. We just cannot so fast to check your
problem. I am happy that problem solved. Hope your answer will help to
other users who will have the same problem.
--> Peter Horsfield (user)  at 17 May 04 05:00 writes

Ok, we resolved this issue.

The MS KB article was correct in its resolution, the problem went away when
we altered the relative path to an absolute path for the Clearcase (atria)
Source code control provider entry.

Even though we were not using Clearcase anymore, it still had to change.

Thanks!
--> Peter Horsfield (user)  at 14 May 04 05:00 writes

Hello, we're having a strange problem with VS.NET and the SCC Proxy.

SCC Proxy was working fine with VS.NET 7.0, however the developer is moving
to VS.NET 7.1 in order to migrate to .NET framework 1.1.

After installation of VS.NET 7.1, accessing source control from the VS.NET
7.1 file/source control/open solution from source control menu caused the
error:

'Unspecified Error'

Attempting any other SCC operations produced the the same message.

We then proceeded to uninstall push ok and reinstall it, but encountered
the same error.

Then we checked the MS KB article
http://support.microsoft.com/?id=820833

But this article, although referencing the same error, did not help.

Finally we reinstalled Visual Studio .NET 2003 and are still having the
same problem.

Have you seen this error before?

Thanks very much for your time,

Peter
Rate this ticket:
Not useful at all
Partially useful
Useful
Very useful



You are 9752093 visitor since 20 Jan 2003.
3047 visitors today and 19 online right now.
blank left to top right blank

© Copyright by PushOk Software, 2003-2024, webmaster@pushok.com