The error code 1612 is the most helpful to determine the root cause. If you perform an error lookup in CMTrace.exe, it will return The installation source for this product is not available. Verify that the source exists and that you can access it.
Anyone out there with any experience in System Center, curious if you've run across this particular error. I am trying to deploy a small application and I'm getting as far as the endpoint downloading the executable into it's ccmcache folder. However the installation fails out with this error after a reboot: Error Code: 0x80070643 (-) Error Description: Fatal error during installation. And this from AppEnforce.log: Process 3660 terminated with exitcode: Looking for exit code - in exit codes table.
installation failed with error code 1612 sccm client not installing
Machine is running with windows XP SP2. I have also tried deleting the wbem/repository but it did not worked. These are the last few lines of ccmsetup.log file, I've dealt with this issue many times, the SMS 2003 Toolkit helps sometimes by deleting all of the old sccm junk prior to upgrading to a new client but sometimes the only thing that does help is a reboot.
I was trying to uninstall one application from SCCM. This application was installed about 4 years ago.I used uninstall option in application based deployment. However, it was failed with error 1612.Again i tried to use the package based uninstallation. It is also failed with 1612.I did some research and created a script to perform the uninstallation.
This error could also occur when downloading and updating with the Adobe Application Manager. The error can be bypassed by downloading the update separately from installing it. That is, save the updater file locally (on your computer) and then run it in a separate step.
I recently ran into error 1612 with a GPO on a 2012 R2 DC that turned out to be related to file name. The install package was named 'Software.Installer.msi' and renaming to 'SoftwareInstaller.msi' fixed the issue...
Most of the time we get this error on software installations, it's because the network share permits domain user read and execute, but the policy is installed by the computer account. You can grant permissions by either adding the domain computers account or more likely replacing domain users with authenticated users which includes domain users and domain computers.
As there are multiple error codes you can start the troubleshooting by resolving each one and seeing if that automatically sorts the other error code issues. To begin with, this Error 1603 when you try to install a Windows Installer package, You may receive this error message if any one of the following conditions is true:
The error codes ERROR_SUCCESS, ERROR_SUCCESS_REBOOT_INITIATED, and ERROR_SUCCESS_REBOOT_REQUIRED are indicative of success. If ERROR_SUCCESS_REBOOT_REQUIRED is returned, the installation completed successfully but a reboot is required to complete the installation operation.
This post from Technet Forums (Thanks to Charlie Hawkins), has inspired us to prepare a list of all error codes, that can happen during the SCCM client installation. Some errors have been added based on our personal experiences.
One of our custom SSRS reports is made especially for the Configuration Manager Client. This report now shows the last SCCM client installation error codes, including the description of the installation deployment state. This report will help you achieve the *near* 100% client installation, that your project manager loves to see.
Error 401 in the iis log indicates authentication issue, so look in the event viewer secutiry log and find the event with the same time stamp found in the iis log.The event shows the error:Log Name: SecuritySource: Microsoft-Windows-Security-AuditingDate: 04-04-2014 10:56:49Event ID: 4625Task Category: LogonLevel: InformationKeywords: Audit FailureUser: N/AComputer: servername.fqdnDescription:An account failed to log on.
SCCM Agent has only two actions after installation:LocationServices 800 (0x320) Signature verification using hash algorithm 32772 failed with 0x80090006.LocationServices 800 (0x320) CCMVerifyMsgSignature failed.LocationServices 800 (0x320) Failed to verify received message 0x80090006LocationServices 800 (0x320) CCMVerify failed with 0x80090006LocationServices 800 (0x320) Failed to verify message. Could not retrieve certificate from MPCERT.LocationServices 800 (0x320) MPCERT requests are throttled for 00:00:00
I had a hunch that it should have something to do with certificates of management points the client computer received because the LocationServices.log implied that the messages coming from the management points could not be verified. It was obviously that the client computer failed to decrypt the messages from the management points.
As you can see, the client computer failed to fill the WMI class instances of SMS_MPInformationEx and SMS_MPListEx. This behaviour corresponded to the error messages in LocationServices.log.
If you are installing Sage 50cloud Accounts and have a different issue with your installation, or the recommended steps have not resolved the problem, please refer to our installation troubleshooting guide.
Perhaps the biggest addition this release is the ability to halt installation if a reboot is detected (#1038). Once you turn this feature on, if you are installing some packages and somewhere in the middle of that there is a need for a reboot, Chocolatey will stop and exit with either exit code 350 (pending reboot prior to anything) or 1604 (install incomplete), indicating a reboot is needed to continue. It won't reboot for you, as it is just a package manager - but it will stop execution so nothing that may error on install is attemtped. You'll need to opt into this feature, so see #1038 for details.
This blogpost describes a method I have used to uninstall Flash 19, when the original source files on the local computer are missing. Although all file names and values are specific to Flash 19, the overall method is generic. So if you have problems with uninstalling a software product because of missing sources (error 1706 : -2147483647 ), continue reading! :)
If there are too many overlay handlers installed and TortoiseSVN does not show any overlays, you can try to delete some of the installed handlers from the registry. But be careful when editing the registry!Why are the icons only visible on local and not on network drives?Go to the Settings -> Look and Feel -> Icon Overlays and check the drive types for which you want to see overlay icons. Be aware that enabling overlays for network drives will slow down not only TortoiseSVN but the whole system.Why are the overlay icons on SUBSTed drives messed up?If your working copy is on a SUBST drive the icons might be mixed up.The problem arises because the cache tries to fetch the status for two "different" locations at the same time, but those locations are actually the same so there are two status fetchings for the same working copy at the same time.There is an easy way to solve this: just exclude the original path from showing overlays (settings->icon overlays->exclude paths).For example, if you have mapped \\station\folder\wc to g: then put \\station\folder\wc* as the exclude pattern.Another way to make the overlays work is to set the "Status cache" setting from "Default" to "Shell".Why are the overlays showing the wrong status?Sometimes you find that the overlays don't reflect the real status of files and/or folders. Usually, hitting the F5 key is enough to make the overlays appear correctly (you might have to wait a few seconds until the cache has fetched the status again).The treeview on the left side of the explorer is a whole other story. It won't update the overlays, no matter how many times you hit the F5 key. That's a problem with the explorer and outside of TortoiseSVN's reach.A short explanation: The treeview always shows the whole explorer tree, including network drives and other namespace extensions. Since these can be very slow (e.g. slow network drives), the explorer tree doesn't ask the overlay extensions for updated overlays all the time. Even if you tell the explorer that a folder has changed and it should update the overlays accordingly, it doesn't do so. It first checks itself if the folder really has changed and only updates the overlays if it thinks the folder really has changed.Now, since the Subversion status of a folder has nothing to do with the folder itself, the folder itself never really changes (only some file inside the .svn folder, but not the folder itself), explorer therefore doesn't update the overlays.There are some tricks and workarounds to make the explorer refresh the overlays even on the left treeview, but those are tricks and workarounds, which obviously don't work all the time.There's one trick that usually works, but it is slow and TortoiseSVN can't use that trick on-the-fly - it just would slow down the system too much. But you can trigger that trick manually by executing the 'cleanup' command on the root of your working copy. After the cleanup command has finished, you have to wait a few seconds for the treeview to update the overlay icons.Why do the overlay icons sometimes change to random graphics?The Windows icon cache is a fairly buggy creature. You can solve this in one of the following ways:Install Microsoft's TweakUI and run the option to rebuild icons.Or increase the icon cache size. Go to HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows\\CurrentVersion\\Explorer and add a new String Value called Max Cached Icons. The default value is 500 - try increasing it to 2048.Or delete the file called ShellIconCache in your Windows directory. And reboot.With TortoiseSVN 1.3.0 and later, you can also rebuild the icon cache by calling TortoiseProc from the command line like this TortoiseProc.exe /command:rebuildiconcacheWhy is there no overlay for 'update available' or 'locked by others'?To show such an overlay, TortoiseSVN would have to contact the repository every time the overlay is shown. That would make explorer impossibly slow. Servers often take several seconds to respond, sometimes minutes - do you really want explorer to hang while that takes place, every time you open a versioned folder?A fundamental design feature of TortoiseSVN is that the repository is never contacted except when explicitly requested by one of the context menu items. Even with that restriction, it is still hard work maintaining a fast response.If you want to see which users have files locked in their working copies or which files need updating, use the Check for Modifications dialog and click on the Check repository button.Overlay icons100% CPU, when I right-click on a file.Every time I right click on a file, the CPU goes to 100% (whilst the right click menu is displayed.) If I select something from the menu, CPU goes back to normal. If I right click on 'nothing' then the CPU is OK. What is happening?XP contains a known bug that causes the CPU usage to spike to 100 percent when you access the context menu under certain configurations. This bug causes file-copy operations to halt, network connections to slow, and streaming media (e.g., audio, video) to become distorted. To work around this bug, you need to disable the GUI's transition effects by performing the following steps:Start the Control Panel Display applet.Select the Appearance tab.Click Effects, then clear the "Use the following transition effect for menus and tooltips" check box.Click OK to close all dialog boxes.Another solution that often works is to left-click the file or folder before right-clicking to display the context menu.Can I create a local repository on a network directory?You can use a repository on a network share, but only as a single user as you would use a local hard drive. The next FAQ item explains why sharing a repository in this way is a Bad Idea (TM). Unless you have really pressing reasons to keep your repository on a network share it is generally best to avoid doing so.If you really need to access a repository on a network share you should do one of the following:Use drive mapping using the syntax below:Map //server/shared to S:file:///S:/repos (3 leading slashes before drive letter)Specify a UNC path directly using the syntax below:Subversion >= 1.2file://server/shared/repos (2 leading slashes)Subversion file://///server/shared/repos (5 leading slashes)file:///\server/shared/repos (3 slashes + backslash)But don't say we didn't warn you...Can I keep my repository on a network share instead of setting up a server?If you need multiple computers to access the repository, you can in theory create a repository on a network share and access it using file:// protocol. In practice this is not recommended for four very good reasons:You are giving direct write access to all users, so they could accidentally delete or corrupt the repository file system.Not all network file sharing protocols support the locking that Subversion requires. One day you will find your repository has been subtly corrupted.You have to set the access permissions in just the right way. SAMBA is particularly difficult in this respect.If one person installs a newer version of the client which upgrades the repository format, then everyone else will be unable to access the repository until they also upgrade to the new client version.By far the best way is to set up a real server process (such as Apache or svnserve), store the repository on a local filesystem which the server can access, and make the repository server available over a network. It is easier than you might think. Chapter 6, Server Configuration in the Subversion Book covers this process in detail.Can I store a working copy on a network share?This depends on the network share. But we really, really urge you to not do this! Even if you're using a Windows server and use those network shares, the fcntl() file locking is not fully reliable. And for Samba based shares all bets are off. Which means you will get a corrupted working copy and you then will lose data! Maybe not today, maybe not tomorrow, but someday you will.If you really must store a working copy on a network share, have a close look at the corresponding FAQ entry of the SQLite project.Can I use different Subversion clients with the same working copy?Yes, you can change from one client to another whenever you want. The clients just control your working copy and the interaction between your working copy and the repository. The metadata inside the working copies used by the different clients is identical.But you can only use different clients if they all use the same version of the Subversion library. The version of the Subversion library that TortoiseSVN uses is indicated in the filename of the installer, other clients have similar indications. You have to make sure that those versions match each other in the first two digits. For example, all clients using Subversion 1.6.x can be used together (the 'x' indicates that this number is not relevant for compatibility).You must also be sure that all the clients are built for the same OS. Client compatibility is only guaranteed for a particular OS type and metadata representations may differ. You must not use a native Windows client and the Cygwin client on the same working copy. And if you share a working copy over a network you must not use a Linux and a Windows client on the same working copy.Can TortoiseSVN convert line breaks in text files on the fly?Check the subversion book about the svn:eol-style property here. If you set that property to e.g. 'native', then the file will have LF line-endings on Linux, but CRLF line-endings on Windows. To see how you can set those properties with TortoiseSVN, read our docs here.How do I find out what the conflict is when it is in a directory's property list?Inside the folder with the conflicting properties, you'll find a file called dir_conflicts.prej. Open that file in a text editor and you will see the conflicting properties. Choose the one you want to keep and overwrite the conflicting property with that one.I accidentally removed a file. How do I get it back?If you haven't committed your changes yet, you can do a revert on the parent folder where you deleted the file or directory.If you have already committed the deleted file, then you can use the repository browser, change to the revision where the file still existed and then use the command Copy to... from the context menu. Enter the path to your working copy as the target and the deleted file will be copied from the repository to your working copy.You can also restore a deleted directory using this technique.If, after the file / folder has been restored using this trick, the log dialog doesn't show you the history of that file, don't worry. The history is still there. If you copy a file in SVN you copy its history too. But the default setting in TSVN's ShowLog is to 'Stop on copy', which means that when you look at the history, it only goes back to the branch point. The reason for this is that when you are looking at a real branch of a project, mostly you only want to see the history of that branch. To see the whole history in ShowLog you need to unselect the 'Stop on copy' checkbox and click on 'Get All'.I get multiple TortoiseSVN context menu entries when I right click on a link!This is by design. One entry is for the link itself (the .lnk-file), the other for the target the link points to. This way a link can both be versioned and in the same time work as a link should by allowing operations on its target. In fact, you can have up to three entries in the file menu (the context menu will show only two).Is it possible to use 'Shared Files' like in Visual Source Safe?Yes, but with some limitations. You can use "File Externals" to pull in single files from a different part of the same repository as your working copy, but not from a foreign repository. You can also share folders, and these can be from any repository. Please look at the chapter External Definitions in the Subversion Book.Is it possible to use TortoiseSVN without a server?Yes, it is. You can use the file:// protocol to access your repository locally. However we strongly recommend that you do this only for testing. For a more detailed explanation please refer to this FAQ entry.Is there a way to send username & password when using TortoiseProc?TortoiseSVN is a GUI client, therefore it will ask you for username and password in case it's needed. If you want to automate access to your repository without user interaction (i.e. without having to enter username and password if needed), use the command line client.How does the revision graph work?The revision graph is a little bit special, it's not like the other features found in TortoiseSVN. It shows a graph of a file or folder through the history with all the revision where the file or folder was copied, moved, branched or tagged.We often get people asking questions why it needs to get the log for the repository root, or why it needs to get the full log from the HEAD revision back down to the first revision.Just to make this clear: this is not because we're lazy programmers, it really is necessary.The revision graph shows the history of a selected file or folder by finding all revisions where the selected item was copied. And the graph has to do that by using the information that is available.If you look at the log messages for your selected file or folder, you can see in the lower pane of the log dialog all affected paths of the selected revision. That information is what we use for the revision graph. You will also notice that if you just show the log for e.g. /trunk, you won't see any entries in the log dialog for revisions which happened in a tag or branch. You won't even see an entry where you tagged or branched /trunk itself in that log. --> that's why we must fetch the log for the repository root: only the log of the repository root will give us all the information we need, including when and where a path has been copied/branched/tagged/moved to.If we would only fetch the log for a specific range and not all revisions, we could miss the revision where (still using the example above with /trunk) the trunk was branched or tagged. And even though there are changes to those branches and tags or they still exist in the revision range, the graph could not know that those branches/tags were made from /trunk and not from some other path. That means, the graph would not just be incomplete, it would be wrong.And no: we will never change that. Because there's nothing worse than a graph that's only sometimes correct - you would never know when and if it is correct, which means it would be worse than useless.Why is there no 'author' shown in the logs when I commit changes via svn+ssh?Since SSH completely takes care of the authentication process, Subversion won't even see the author who does the commit. So to tell Subversion an author you have to specify the author in the URL itself. E.g. svn+ssh://[email protected] You should do that when you check out your working copy.Why does TortoiseSVN not recognize that a file has been modified?If you have modified a file, but TortoiseSVN does not recognize that the file has been modified, please first check whether the file really differs from what you have in your working copy.If you know for sure that the file has modifications and it still does not show up as modified in the commit dialog, make sure thatthe file 'last modification' date has changed (some tools like hex editors like to reset that time)if the svn:eol-style property is set and the changes are only to newlines, the file won't show up as modified because for Subversion it hasn't changedSubversion determines whether a file has changed with the following approach:has the 'last modification' date and/or the file size changed?if not: file is not modifiedif yes: compare file content with the BASE filestop at the first byte that differs, mark the file as modifiedif no byte differs regarding to BASE, mark the file as not-modifiedWhen I remove a file it vanishes, how do I commit it?Easy, you commit the whole directory! Right-click in the Explorer window next to the file, and choose commit. The commit dialog will show you every modification as well as added or deleted files.Permission problems with working copies on a SAMBA share.After upgrading to TortoiseSVN 1.5.x or later, you get a lot of "Access denied" errors for most of the Subversion commands if your working copy is stored on a SAMBA share.Some users reported that the problem went away after they upgraded SAMBA to the latest version. If that does not help or you can't upgrade, allow readonly files to be deleted in the SAMBA config file:[global]delete readonly = yesFor older versions, try:[global]create mask = 0644force create mode = 0600security mask = 0555force security mode = 0600The information we have received suggests that the main problem is fixed in SAMBA 3.2.3. There is a supplementary problem with making files with the svn:needs-lock property read-only. This is reported to be fixed in SAMBA 3.2.6 or 3.3.0.Browsing very slow in explorer and file/open dialog.If you have mapped network drives which are not resolved, either because the drive is inaccessible, or you have not logged in, file browsing may become unresponsive while Windows tries unsuccessfully to access the drive. Either unmap the drive or ensure that it can be accessed.The bugtraq: properties don't work for dialogs started from the repository browser.This is by design. The repository browser does not read the properties, because that is a very slow operation if done remotely. It's only fast enough when read from a local working copy.If TortoiseSVN would read those properties directly from the repository, it could take several seconds (even minutes!) to fetch them.Showing the log often crashes.The log cache relies on all repositories having different uuids. A detailed explanation about why and what you can do about this is here: 're aware that many Subversion hosting companies made the mistake of not creating new repositories for customers but simply copied a template repository. If you're using such a hoster, please tell them to fix this problem.When I update a working copy, new files are not added!Between TortoiseSVN 1.6.0 and 1.6.1, added folders were added with a depth of "Only this item". This lead to a so called "sparse checkout" of that part of your working copy.Please update to the latest version of TortoiseSVN to avoid such problems in the future.To fix your sparse working copy, instead of "Update", use the "Update to revision..." command from the TortoiseSVN submenu (right-click in explorer), change the "Update depth" combobox to "Fully recursive".I was told that issue/bug X was fixed in rXXX, but the latest release still doesn't have this implemented/fixed?Our release policy is to never introduce new features or resource changes on the stable branch. We work on the trunk, where we fix bugs, introduce new features or change the behavior of features. Only important bugfixes are merged back to the stable branch, and the stable branch is where we create our releases from.We have this policy to prevent getting new bugs into the stable branch. After all, it's called the stable branch.Your requested feature/reported bug, even though it is fixed/implemented on trunk was not merged back to the stable branch due to this policy. That's why you don't see the change in the latest release.You can use a nightly build if you feel adventurous though: does not work well with EclipseEclipse copies directories as part of its normal operation, and in a subversion working copy it will copy the .svn directory as well. This causes TortoiseSVN to think that there are versioned files in the bin directory.If you want to keep using TortoiseSVN and just prevent this from happening, you need to add '**/.svn/' to Eclipse's source exclude list.But Eclipse has its very own subversion plugin called Subclipse, which makes Eclipse SVN-aware and fixes the problem at source. You can find it at After you install Subclipse you need to make a fresh checkout. It will not fix checkouts that were made before it was installed.Security warnings when uploading files in Internet ExplorerWhen you select files to upload using a web form in Internet Explorer, you may get security warnings saying that a program is trying to open web content, identifying TortoiseSVN as the culprit.Don't panic! This is a (mis) feature of the Internet Explorer security model. Since TortoiseSVN is a shell extension it loads automatically whenever a file-open dialog is created, in order to provide the icon overlays and context menus.There are two ways to stop the warnings:In TortoiseSVN's settings go to the Icon Overlay section and check the box Show overlays and context menu only in Explorer.When the warning appears, check the box marked never show for this application again.Repeated dialogs to insert smart cardIf you're using a smart card software, you might get a dialog asking you to insert your smart card every time TortoiseSVN tries to connect to a repository.Unfortunately some smart card vendors consider this not a bug but a feature, even though it doesn't server any purpose other than annoying users.To prevent TortoiseSVN from trying to access the Windows cert store in case a certificate is requested by the repository, create the registry key HKCU\Software\TortoiseSVN\OpenSSLCapi as a DWORD and set its value to 0."compare with working copy" does not use the configured diff viewerWhen you run a "compare with working copy" from the log dialog, TortoiseMerge is started even if you have configured a different diff viewer tool to be used.This is not a bug: this command does not compare two files even though it may appear like it. It actually creates a patch file and then starts TortoiseMerge to show what applying that patch file to the working copy would look like. And since we don't know of any other UI tool that can apply patch files, TortoiseMerge is started. Your configured diff viewer can not do that.Where are the debug symbols?All debug symbols, both for the official releases and the nightly builds are hosted on DrDump.comTo access the debug symbols, configure your debugger to use the symbol server at -server.com:8080/public/tsvn/71040F62-F78A-4953-B5B3-5C148349FED7/symsrvTo figure out how to use a debug symbol server, have look at this article.How can I...... add keyword information like author, revision, date and commit-time to my files?Read about the Subversion property svn:keywords in the Subversion book.With TortoiseSVN, set the properties as described here.... change the case of a filename?Subversion is designed to work with case-sensitive file systems such as are used on Linux. When it comes to the Windows case-insensitive file system, things do not always run as you might expect. A case in point is renaming a file where only the case changes, e.g. renaming Makefile to MAKEFILE. Prior to Subversion 1.7 you could not do this easily within your working copy as Subversion required both names to exist simultaneously for a short time, and Windows cannot support this.By far the easiest way is to rename directly using the repository browser:Commit the changes in your working copy.Rename the file from UPPERcase to upperCASE directly in the repository using the repository browser.Update your working copy.As of Subversion 1.7 this is no longer a problem as the whole working copy structure was changed, so files can simply be renamed using the normal TSVN->Rename command.... change the log message or author after committing?Call up the log dialog and do a Right-Click on the revision you want to edit. Then select "change author" or "change log message" from the context menu. To make the server accept these changes, a pre-revprop-change hook, that allows to change author or message, has to be installed for the repository. The default installation rejects changes to author and log message.... clear the drop-down lists in TortoiseSVN?You can clear all the stored data from the settings dialog of TortoiseSVN. Just click on the corresponding button.Single items can be permanently removed from drop-down lists by pressing Shift-Delete.... completely remove a repository from my computer?Aehemm: select the folder and hit Delete (the key on your keyboard may be labelled only Del).Seriously, there are no hidden files or settings. The repository is completely contained in one folder tree.The same applies to working copies. If you send a working copy to the recycle bin it can seriously slow down future deletes because of the large number of small files. You may want to empty the recycle bin soon after.... export the log out to a text file?Use the log dialog. Select all the entries you want and press Ctrl+C. Then use Ctrl+V (or paste) in your favourite text editor.If you want to process the log messages automatically or you need them in xml format, you can use the command line client for that.... get the project revision number into my project?If you want the revision number in your program version number, you need an additional tool to do that. You can find the tool SubWCRev.exe on the download page on our website or in your TortoiseSVN Folder under bin.This tool traverses your whole working copy for the most recent revision. Once that revision is found, it replaces all occurrences of the following strings:$WCREV$This string will be replaced by the revision number of your working copy.WCMODS?Modified:Not modified$If you have local modifications, the string between question mark and colon will be inserted. If you have no local modifications, the string between colon and dollar sign will be inserted. In our example above Modified or Not modified.$WCDATE$Will be replaced by the date of the highest revision in your working copy.As an example, have a look at the file version.in in the TortoiseSVN source tree. This file is used in TortoiseSVN and its resource files. The SubWCRev.exe tool is called from the build script like this: SubWCRev.exe path\\to\\working\\copy version.in version.h This creates a new file version.h with all the strings above replaced with the values of the working copy. The version.h file is then used in the project itself and included in the resource files for the version information.... prevent Subversion from doing automatic merges?Some people don't like the fact that Subversion merges changes from others with their own local working copy changes automatically on update. Here's how to force those files into a conflicted state so you can merge manually at your convenience.In TortoiseSVN->Settings->Subversion configuration file, click on the edit button.Change the [helpers] section by adding diff-cmd = "C:\\false.bat" diff3-cmd = "C:\\false.bat" (note the double backslash)Create the file C:\false.bat which contains two lines@type %9@exit 1This effectively makes auto-merge fail every time, forcing the file into conflict.The reason for the curious 'type %9' line is that the diff3-cmd sends the merged output to stdout. Subversion then takes this and overwrites your local file with the merge results. Adding this line avoids getting an empty local file.... see what my current sandbox/repository is?Right-click on the folder in your working copy, choose "Properties" from the explorer context menu. Then, in the properties dialog, switch to the "Subversion" tab. There you can see all sorts of information about the selected folder, including to what URL it points to.Another quick way of seeing this information is to select "Relocate" from the context menu and look at the first URL. Since you don't want to relocate your WC, just abort this dialog.... install TortoiseSVN silently/automatically?Just start the MSI installer like this: 2ff7e9595c
Commenti