stackemedia

cvs server: sticky tag _ for file _ is not a branch

This was posted in Development, Error Solutions on September 2nd, 2010

We use TortoiseCVS for version control, today I got the error

cvs server: sticky tag ” for file ” is not a branch … correct the above errors first!

This was caused by getting a previous revision of the file and trying to commit a change to that file; however you can only commit to HEAD.

To get rid of this error and commit your changes, right-click the file, CVS > Update Special > Check “Get tag/branch/revision” > select HEAD > click OK.

You should then be able to commit your changes.

Our TortoiseCSV version is 1.10.10

IIS ASP.NET tab not showing

This was posted in Error Solutions on July 6th, 2009

Platform: Windows Server 2003
Issue: ASP.NET tab not showing in IIS; thus unable to select dotnet version.
Solution:

1. Uninstall IIS
2. Reboot server
3. Install IIS
4. Open the command prompt (start, run, “cmd”)
5. Type: “cd C:\WINDOWS\Microsoft.NET\Framework\v1.x.xxxx”
6. Type: “aspnet_regiis.exe -i”
7. Type: “cd …”
8. Type: “cd v2.x.xxxxx”
9. Type: “aspnet_regiis.exe -i”
10. Open iis (start, run, “inetmgr”)
11. Check that the ASP.NET tab is visible and that you can change the version of .net.

Error 1718. File FileName was rejected by digital signature policy (VS.NET)

This was posted in Error Solutions on June 17th, 2009
Error: “…\Windows\Installer\{some value}.msp did not pass the digital signature check”
(Error 1718. File FileName was rejected by digital signature policy.)
Platform: Windows Server 2003
Task: Installing Visual Studio 2005 SP1
Solution: Download the patch from Microsoft located at http://go.microsoft.com/fwlink/?LinkID=73863

Content controls have to be top-level controls (VS.NET)

This was posted in Error Solutions on June 17th, 2009
Error: “Content controls have to be top-level controls in a content page or a nested master page that references a master page”
Platform: Windows Server 2003 / Visual Studio 2008
Task: Viewing a new page created in a project containing a Master Page, which had not been set to use Master Page at creation.
Solution: A solution may be found at

http://www.net-aspect.com/Articles/Error–Content-controls-have-to-be-top-level-controls-in-a-content-page-or-a-nested-master-page-that-references-a-master-page.aspx

TF10121: The path ” is not found or not supported. Type or select a different path (VS.NET)

This was posted in Error Solutions on June 17th, 2009
Error: TF10121: The path ” is not found or not supported. Type or select a different path
Platform: Windows Server 2003
Task: Removing a project from one solution and adding it to another.
Solution: The problem is that a stale reference to the old project is still stored and when we add the
project, it gets back an empty string when we try to get its old directory path.

To workaround, close the original solution and new solution. Re-open the new solution and re-add
the project. It should now add properly.

Still doesn’t add properly? Try removing all Source Safe Bindings:
1. Open project file (csproj) and delete the lines similar to:

<SccProjectName>SAK</SccProjectName>
<SccLocalPath>SAK</SccLocalPath>
<SccAuxPath>SAK</SccAuxPath>
<SccProvider>SAK</SccProvider>

2. Delete source safe files (i.e. *.vspscc)

“JFolder::create: Infinite loop detected” (Joomla)

This was posted in Error Solutions on June 17th, 2009
Error: “JFolder::create: Infinite loop detected”
Platform: Joomla 1.5.0
Task: When uploading and installing a new module or plugin.
Solution: 1. Admin site > Help > system info > Directory Permissions
Check that tmp/ is writtable. If not, check that tmp folder exists
in site root and has necessary permissions.

2. Site > Global Configuration > Server
Check Path to Temp-folder under “Server Settings”. Value should point
to tmp folder in site root.

COMException (0×800a01b0) (.NET)

This was posted in Error Solutions on June 17th, 2009
Error: “COMException (0×800a01b0): File name or class name not found during Automation operation”
Platform: Windows XP Pro SP2
Task: Running a asp.net 1.1 legacy application that uses a COM+ component to access a database via a udl file.
Solution: Ensure that the udl file is located in the correct location and has the right name.

Tested browsers: firefox, chrome, IE8