I am programming in c# and want to copy a folder with subfolders from a flash disk to startup.
Here is my code:
private void copyBat()
{
try
{
string source_dir = "E:\Debug\VipBat";
string destination_dir = "C:\Users\pc\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup";
if (!System.IO.Directory.Exists(destination_dir))
{
System.IO.Directory.CreateDirectory(destination_dir);
}
// Create subdirectory structure in destination
foreach (string dir in Directory.GetDirectories(source_dir, "*", System.IO.SearchOption.AllDirectories))
{
Directory.CreateDirectory(destination_dir + dir.Substring(source_dir.Length));
}
foreach (string file_name in Directory.GetFiles(source_dir, "*.*", System.IO.SearchOption.AllDirectories))
{
File.Copy(file_name, destination_dir + file_name.Substring(source_dir.Length), true);
}
}
catch (Exception e)
{
MessageBox.Show(e.Message, "HATA", MessageBoxButtons.OK, MessageBoxIcon.Warning);
}
}
I got an error:
Could not find a part of the path E:DebugVipBat
David Rogers
2,5664 gold badges39 silver badges82 bronze badges
asked Feb 15, 2014 at 11:10
6
The path you are trying to access is not present.
string source_dir = "E:\Debug\VipBat\{0}";
I’m sure that this is not the correct path. Debug folder directly in E: drive looks wrong to me. I guess there must be the project name folder directory present.
Second thing; what is {0} in your string. I am sure that it is an argument placeholder because folder name cannot contains {0} such name. So you need to use String.Format() to replace the actual value.
string source_dir = String.Format("E:\Debug\VipBat\{0}",variableName);
But first check the path existence that you are trying to access.
answered Feb 15, 2014 at 11:14
SachinSachin
39.8k7 gold badges88 silver badges102 bronze badges
3
There’s something wrong. You have written:
string source_dir = @"E:\Debug\VipBat\{0}";
and the error was
Could not find a part of the path EDebugVCCSBat
This is not the same directory.
In your code there’s a problem, you have to use:
string source_dir = @"E:DebugVipBat"; // remove {0} and the \ if using @
or
string source_dir = "E:\Debug\VipBat"; // remove {0} and the @ if using \
Tom Bowen
7,9544 gold badges21 silver badges40 bronze badges
answered Feb 15, 2014 at 11:21
AkremAkrem
4,9838 gold badges35 silver badges62 bronze badges
0
Is the drive E a mapped drive? Then, it can be created by another account other than the user account. This may be the cause of the error.
Daniel B
8,6415 gold badges45 silver badges75 bronze badges
answered Sep 24, 2015 at 14:57
ThorstenCThorstenC
1,24411 silver badges26 bronze badges
2
I had the same error, although in my case the problem was with the formatting of the DESTINATION path. The comments above are correct with respect to debugging the path string formatting, but there seems to be a bug in the File.Copy exception reporting where it still throws back the SOURCE path instead of the DESTINATION path. So don’t forget to look here as well.
-TC
answered Dec 10, 2015 at 5:03
TJCTJC
911 silver badge4 bronze badges
Probably unrelated, but consider using Path.Combine instead of destination_dir + dir.Substring(...). From the look of it, your .Substring() will leave a backlash at the beginning, but the helper classes like Path are there for a reason.
answered Nov 20, 2015 at 17:53
Drew DelanoDrew Delano
1,33115 silver badges21 bronze badges
There can be one of the two cause for this error:
- Path is not correct — but it is less likely as CreateDirectory should create any path unless path itself is not valid, read invalid characters
- Account through which your application is running don’t have rights to create directory at path location, like if you are trying to create directory on shared drive with not enough privileges etc
answered Feb 8, 2017 at 13:35
1
File.Copy(file_name, destination_dir + file_name.Substring(source_dir.Length), true);
This line has the error because what the code expected is the directory name + file name, not the file name.
This is the correct one
File.Copy(source_dir + file_name, destination_dir + file_name.Substring(source_dir.Length), true);
ArunPratap
4,5887 gold badges28 silver badges43 bronze badges
answered Sep 14, 2015 at 0:29
Ryan ChongRyan Chong
1802 silver badges13 bronze badges
0
We just had this error message occur because the full path was greater than 260 characters — the Windows limit for a path and file name. The error message is misleading in this case, but shortening the path solved it for us, if that’s an option.
answered Jun 15, 2022 at 18:02
RealHandyRealHandy
5042 gold badges7 silver badges25 bronze badges
I resolved a similar issue by simply restarting Visual Studio with admin rights.
The problem was because it couldn’t open one project related to Sharepoint without elevated access.
answered Oct 3, 2016 at 7:03
0
This could also be the issue: Space in the folder name
Example:
Let this be your path:
string source_dir = @»E:DebugVipBat»;
If you try accessing this location without trying to check if directory exists, and just in case the directory had a space at the end, like :
«VipBat «, instead of just «VipBat» the space at the end will not be visible when you see in the file explorer.
So make sure you got the correct folder name and dont add spaces to folder names. And a best practice is to check if folder exists before you keep the file there.
answered Feb 11, 2022 at 4:49
Reejesh PKReejesh PK
6181 gold badge11 silver badges24 bronze badges
- Remove From My Forums
-
Question
-
I run an application on the server, get this error «Could not find a part of the path».
The partial code is
string outPath = @"2222-ffffDataWorkBMS"; string chrName = "chr{0}.psd"; FileWriter[] fwChr = new FileWriter[45]; for (int i = 0; i < fwChr.Length; i++) { fwChr[i] = new FileWriter(Path.Combine(outPath, string.Format(chrName, i + 1))); }
Thanks for help.
Answers
-
Are you sure C:TestBMS exists?
-
Marked as answer by
Thursday, November 25, 2010 2:49 PM
-
Marked as answer by
-
Resloved it already. My fault.
-
Marked as answer by
ardmore
Friday, November 26, 2010 11:28 PM
-
Marked as answer by
Steps to reproduce
Define that in your project.json:
"tools": {
"dotnet-ef": "1.0.0-*"
},
dependency: "Microsoft.EntityFrameworkCore.Tools": "1.0.0-preview1-final",
then SAVE!
Now the nuget restore starts in Visual studio but I get this error among the other error below:
error: Unable to resolve 'dotnet-ef (>= 1.0.0)' for '.NETCoreApp,Version=v1.0'.
info : Committing restore...
log : Writing lock file to disk. Path: C:TGB.CoreTGB.Apiproject.lock.json
log : C:TGB.CoreTGB.ApiTGB.Api.xproj
log : Restore failed in 1915ms.
Errors in C:TGB.CoreTGB.ApiTGB.Api.xproj
Unable to resolve 'dotnet-ef (>= 1.0.0)' for '.NETCoreApp,Version=v1.0'.
Why is this nuget: Microsoft.EntityFrameworkCore.Tools not compatible — somehow — with my
framework: net461 project?
I get this error:
Severity Code Description Project File Line Suppression State
Error Could not find a part of the path ‘C:Usersbastien.nugetpackages.toolsdotnet-ef’. TGB.Api C:Program Files (x86)MSBuildMicrosoftVisualStudiov14.0DotNetMicrosoft.DotNet.Common.Targets 241
Line 241 is:
<Dnx
RuntimeExe="$(SDKToolingExe)"
Condition="'$(_DesignTimeHostBuild)' != 'true'"
ProjectFolder="$(MSBuildProjectDirectory)"
Arguments="$(_BuildArguments)"
/>
Actual behavior
When I do run «dotnet ef —help» in the TGB.Api project directory on the CMD I get this error:
C:TGB.CoreTGB.Api>dotnet ef —help
Unhandled Exception: System.IO.DirectoryNotFoundException: Could not find a part of the path 'C:Usersbastien.nugetpackages.toolsdotnet-ef'.
at System.IO.Win32FileSystemEnumerableIterator`1.CommonInit()
at System.IO.Win32FileSystemEnumerableIterator`1..ctor(String path, String originalUserPath, String searchPattern, SearchOption searchOption, SearchResultHandler`1 resultHandler)
at System.IO.Win32FileSystemEnumerableFactory.CreateFileNameIterator(String path, String originalUserPath, String searchPattern, Boolean includeFiles, Boolean includeDirs, SearchOption searchOption)
at System.IO.Win32FileSystem.EnumeratePaths(String fullPath, String searchPattern, SearchOption searchOption, SearchTarget searchTarget)
at System.IO.Directory.EnumerateFileSystemNames(String path, String searchPattern, SearchOption searchOption, Boolean includeFiles, Boolean includeDirs)
at System.IO.Directory.EnumerateDirectories(String path)
at Microsoft.DotNet.Cli.Utils.ToolPathCalculator.GetAvailableToolVersions(String packageId)
at Microsoft.DotNet.Cli.Utils.ToolPathCalculator.GetBestLockFilePath(String packageId, VersionRange versionRange, NuGetFramework framework)
at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.GetToolLockFilePath(LibraryRange toolLibrary, String nugetPackagesRoot)
at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.GetToolLockFile(LibraryRange toolLibrary, String nugetPackagesRoot)
at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.ResolveCommandSpecFromToolLibrary(LibraryRange toolLibraryRange, String commandName, IEnumerable`1 args, ProjectContext projectContext)
at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.ResolveCommandSpecFromAllToolLibraries(IEnumerable`1 toolsLibraries, String commandName, IEnumerable`1 args, ProjectContext projectContext)
at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.ResolveFromProjectTools(String commandName, IEnumerable`1 args, String projectDirectory)
at Microsoft.DotNet.Cli.Utils.ProjectToolsCommandResolver.Resolve(CommandResolverArguments commandResolverArguments)
at Microsoft.DotNet.Cli.Utils.CompositeCommandResolver.Resolve(CommandResolverArguments commandResolverArguments)
at Microsoft.DotNet.Cli.Utils.CommandResolver.TryResolveCommandSpec(String commandName, IEnumerable`1 args, NuGetFramework framework, String configuration, String outputPath)
at Microsoft.DotNet.Cli.Utils.Command.Create(String commandName, IEnumerable`1 args, NuGetFramework framework, String configuration, String outputPath)
at Microsoft.DotNet.Cli.Program.ProcessArgs(String[] args, ITelemetry telemetryClient)
at Microsoft.DotNet.Cli.Program.Main(String[] args)
Expected behavior
When I do «dotnet ef —helpf» on the CMD I expect to get the help…
Environment data
dotnet --info output:
.NET Command Line Tools (1.0.0-preview1-002702)
Product Information:
Version: 1.0.0-preview1-002702
Commit Sha: 6cde21225e
Runtime Environment:
OS Name: Windows
OS Version: 10.0.10586
OS Platform: Windows
RID: win10-x64
I am getting this error «Could not find a part of the path ‘c:usersmehdidocumentsvisual studio 2012ProjectsGridGridData Files’. when downloading a file saved in the above directory.Code for downloading is:
protected void LinkButton1_Click(object sender, EventArgs e) { LinkButton lnkbtn = sender as LinkButton; GridViewRow gvrow = lnkbtn.NamingContainer as GridViewRow; string filePath = GridView1.DataKeys[gvrow.RowIndex].Value.ToString(); Response.TransmitFile(Server.MapPath("~/Data Files/")); Response.End(); }
Please help..
Perhaps what you need to do it specify a single file, instead of a folder?
Response.TransmitFile(Server.MapPath("~/Data Files/"));
Did you mean:
Response.TransmitFile(Server.MapPath("~/Data Files/" + filePath));
I hope our dialog in the comments to the questions helped to resolve your problem. If not, your follow-up questions will be welcome.
This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)
CodeProject,
20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8
+1 (416) 849-8900
Problem
User launches Controller. User chooses database, and enters their username/password. User clicks OK, and receives an error. After clicking OK (to acknowlege the error) the Controller client appears.
Symptom
Information
Standard Error
Number: 76
Source: mscorlib
Description: Could not find a part of the path ‘C:UsersUSERNAMEAppDataRoamingCognosCCRUSERdatabasename’.
at Microsoft.VisualBasic.ErrObject.Raise(Int32 Number, Object
Source, Object Description …
<…>
[OK]
Cause
There are several possible causes for similar errors.
- TIP: For more examples, see separate IBM Technote #1642447.
This Technote specifically relates to the scenario where the cause is invalid cache files inside the end user’s profile.
More Information
By default, Controller stores cache files inside the folder %APPDATA%CognosCCR
- These cache files are used to speed up the system (for the end users), for example when they are given menus to select parameters (for example ‘company’, ‘actuality’ and so on).
These cache files can potentially become invalid/corrupt if the Controller client crashes unexpectedly (for example, the user received an error the last time that they used Controller).
- Therefore, the exact root cause (for why the cache files became corrupt in the first place) can have many potential reasons, but one of them is that the customer is running an old version of Controller which contains a bug (which causes the Controller program to crash unexpectedly).
Resolving The Problem
Long term fix:
Stop the Controller program from unexpectedly crashing during use. In general terms, this means:
- Upgrade to the latest version of Controller (to avoid known bugs)
- Ensure that your environment is in good condition (for example there are no network problems)
Short-Term (instant) Workaround:
Delete local cache files on client device.
Steps:
There are several different methods to delete cache files. Choose the method that is easiest/best for your environment:
- Method #1 — Manual reset of entire CCR folder
- For example: C:UsersBADUSERAppDataRoamingCognos
- For example: C:UsersBADUSERAppDataRoamingCognosccr
- In other words, delete all the *.DSS and *.DSD files (do not delete «ccr.config»):
1. Launch Windows Explorer
2. Browse to the parent of the folder location mentioned in the error message
3. Rename the subfolder ‘CCR’ (for example to CCR.OLD)
4. Test.
Method #2 — Manual (quick and easy, assuming that user can open Controller successfully)
1. Launch Controller
2. Acknowledge error message, and continue into the main Controller client
3. Click «Maintain — Special Utilities — Clear Local Cache’.
Method #3 — Manual deletion of individual cache files.
1. Launch Windows Explorer
2. Browse to the folder location mentioned in the error message
3. Delete all the files in the folder *except* for the file «ccr.config»
Longer-Term Workaround:
Reconfigure Controller so that it always deletes its local cache files (on the client device) each and every time that the user exits Controller.
- NOTE: This method only works for Controller 10.1.364 or later.
- 1. Launch Controller
- TIP: For more details, see separate IBM Technote #1499456.
2. Choose the relevant database (for example «production»)
3. Logon as an administrator
4. Click «Maintain — Configuration — General«
5. Click tab «Server Preferences«
6. Inside «Variable Name» type «CLEARCACHEONEXIT«
7. Inside «Variable Value» type «TRUE«
8. Click Save
9. Close Controller
10. Repeat the above steps for each and every database connection where you want this behaviour to occur.
Related Information
[{«Product»:{«code»:»SS9S6B»,»label»:»IBM Cognos Controller»},»Business Unit»:{«code»:»BU059″,»label»:»IBM Software w/o TPS»},»Component»:»Controller»,»Platform»:[{«code»:»PF033″,»label»:»Windows»}],»Version»:»10.2.1;10.2.0;10.1.1;10.1″,»Edition»:»»,»Line of Business»:{«code»:»LOB10″,»label»:»Data and AI»}}]
clean SC 2012 R2 RTM.
1. had problems with WSUS installation/post configuration
2. found a blog with an identical problem where the problem was solved with the call to Microsoft. Tools directory was missing.
I followed the suggestion: reinstalled WSUS using ps and wsusutil.
I canceled WSUS configuration at recommended step. Everything looked fine.
But after SUP creation I found SMS_WSUS_CONFIGURATION_MANAGER warning.
I checked WCM.log and found Could not find a part of the path ‘C:Program FilesUpdate ServicesSchemabaseapplicabilityrules.xsd’.
When checked there was no Schema folder in the path above. So it’s just missing as folder TOOLS before troubleshooting.
Any suggestions for fixing this.
Thanks.
Here is partial WCM that could help to find the issue, I clearly see that there is no Schema directory in C:Program FilesUpdate Services:
Attempting connection to WSUS server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:00 PM 4536 (0x11B8)
Successfully connected to server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:00 PM 4536 (0x11B8)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:00 PM 4536 (0x11B8)
No changes — WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:00 PM 4536 (0x11B8)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:00 PM 4536 (0x11B8)
Attempting connection to WSUS server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:00 PM 4536 (0x11B8)
Successfully connected to server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:00 PM 4536 (0x11B8)
Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:14 PM 4536 (0x11B8)
Attempting connection to WSUS server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:20 PM 4536 (0x11B8)
Successfully connected to server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:20 PM 4536 (0x11B8)
Successfully inserted WSUS Enterprise Update Source object {91F81925-CC1D-40C0-98C3-902AD3717594} SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:21 PM 4536 (0x11B8)
Configuration successful. Will wait for 1 minute for any subscription or proxy changes SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:09:21 PM 4536 (0x11B8)
Setting new configuration state to 2 (WSUS_CONFIG_SUCCESS) SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:21 PM 4536 (0x11B8)
Attempting connection to WSUS server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:21 PM 4536 (0x11B8)
Successfully connected to server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:21 PM 4536 (0x11B8)
Attempting connection to WSUS server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:22 PM 4536 (0x11B8)
Successfully connected to server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:22 PM 4536 (0x11B8)
PublishApplication(8427071A-DA80-48C3-97DE-C9C528F73A2D) failed with error System.IO.DirectoryNotFoundException: Could not find a part of the path ‘C:Program FilesUpdate ServicesSchemabaseapplicabilityrules.xsd’.~~ at System.IO.__Error.WinIOError(Int32
errorCode, String maybeFullPath)~~ at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath,
Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)~~ at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)~~
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)~~ at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)~~ at System.Xml.XmlTextReaderImpl.FinishInitUriString()~~
at System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext)~~ at System.Xml.Schema.XmlSchemaSet.Add(String targetNamespace, String schemaUri)~~ at Microsoft.UpdateServices.Administration.Internal.UpdateServicesPackage.Verify(String
packageFile)~~ at Microsoft.UpdateServices.Administration.Internal.UpdateServicesPackage..ctor(String packageFile)~~ at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String sdpFile)~~ at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String
sdpFile)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile) SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:22 PM 4536 (0x11B8)
ERROR: Failed to publish sms client to WSUS, error = 0x80070003 SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:22 PM 4536 (0x11B8)
STATMSG: ID=6613 SEV=E LEV=M SOURCE=»SMS Server» COMP=»SMS_WSUS_CONFIGURATION_MANAGER» SYS=confman.contoso.lan SITE=MON PID=1716 TID=4536 GMTDATE=Sat Dec 07 22:10:22.831 2013 ISTR0=»8427071A-DA80-48C3-97DE-C9C528F73A2D» ISTR1=»5.00.7958.1000″
ISTR2=»» ISTR3=»» ISTR4=»» ISTR5=»» ISTR6=»» ISTR7=»» ISTR8=»» ISTR9=»» NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:22 PM 4536 (0x11B8)
Failed to publish client with error = 0x80070003 SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:22 PM 4536 (0x11B8)
completed checking for client deployment SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:22 PM 4536 (0x11B8)
HandleSMSClientPublication failed. SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:22 PM 4536 (0x11B8)
Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:10:22 PM 4536 (0x11B8)
Shutting down… SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:51:31 PM 4536 (0x11B8)
Shutting Down… SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:51:31 PM 4536 (0x11B8)
SMS_EXECUTIVE started SMS_WSUS_CONFIGURATION_MANAGER as thread ID 4168 (0x1048). SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:38 PM 2008 (0x07D8)
This confman.contoso.lan system is the SMS Site Server. SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:42 PM 4168 (0x1048)
Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:42 PM 4168 (0x1048)
Setting new configuration state to 1 (WSUS_CONFIG_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:42 PM 4168 (0x1048)
Changes in active SUP list detected. New active SUP List is: SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:42 PM 4168 (0x1048)
SUP0: confman.contoso.lan, group = CONFMAN, nlb = SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:42 PM 4168 (0x1048)
Updating active SUP groups… SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:42 PM 4168 (0x1048)
Waiting for changes for 1 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:42 PM 4168 (0x1048)
Wait timed out after 0 minutes while waiting for at least one trigger event. SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:43 PM 4168 (0x1048)
Timed Out… SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:53 PM 4168 (0x1048)
Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608) SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:53 PM 4168 (0x1048)
Checking runtime v2.0.50727… SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:53 PM 4168 (0x1048)
Did not find supported version of assembly Microsoft.UpdateServices.Administration. SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:53 PM 4168 (0x1048)
Checking runtime v4.0.30319… SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:53 PM 4168 (0x1048)
Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.3.9600.16384 SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:53 PM 4168 (0x1048)
Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.3.9600.16384 SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:53 PM 4168 (0x1048)
Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:53 PM 4168 (0x1048)
Attempting connection to WSUS server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:53 PM 4168 (0x1048)
Successfully connected to server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:55 PM 4168 (0x1048)
Verify Upstream Server settings on the Active WSUS Server SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:55 PM 4168 (0x1048)
No changes — WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:56 PM 4168 (0x1048)
Setting new configuration state to 4 (WSUS_CONFIG_SUBSCRIPTION_PENDING) SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:56 PM 4168 (0x1048)
Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:56 PM 4168 (0x1048)
Attempting connection to WSUS server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:56 PM 4168 (0x1048)
Successfully connected to server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:53:56 PM 4168 (0x1048)
Successfully refreshed categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:54:27 PM 4168 (0x1048)
Attempting connection to WSUS server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:54:32 PM 4168 (0x1048)
Successfully connected to server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:54:32 PM 4168 (0x1048)
Configuration successful. Will wait for 1 minute for any subscription or proxy changes SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:54:32 PM 4168 (0x1048)
Setting new configuration state to 2 (WSUS_CONFIG_SUCCESS) SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:32 PM 4168 (0x1048)
Attempting connection to WSUS server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:32 PM 4168 (0x1048)
Successfully connected to server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:32 PM 4168 (0x1048)
Attempting connection to WSUS server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:34 PM 4168 (0x1048)
Successfully connected to server: confman.contoso.lan, port: 8530, useSSL: False SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:34 PM 4168 (0x1048)
PublishApplication(8427071A-DA80-48C3-97DE-C9C528F73A2D) failed with error System.IO.DirectoryNotFoundException: Could not find a part of the path ‘C:Program FilesUpdate ServicesSchemabaseapplicabilityrules.xsd’.~~ at System.IO.__Error.WinIOError(Int32
errorCode, String maybeFullPath)~~ at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath,
Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)~~ at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)~~
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize)~~ at System.Xml.XmlUrlResolver.GetEntity(Uri absoluteUri, String role, Type ofObjectToReturn)~~ at System.Xml.XmlTextReaderImpl.FinishInitUriString()~~
at System.Xml.XmlReaderSettings.CreateReader(String inputUri, XmlParserContext inputContext)~~ at System.Xml.Schema.XmlSchemaSet.Add(String targetNamespace, String schemaUri)~~ at Microsoft.UpdateServices.Administration.Internal.UpdateServicesPackage.Verify(String
packageFile)~~ at Microsoft.UpdateServices.Administration.Internal.UpdateServicesPackage..ctor(String packageFile)~~ at Microsoft.UpdateServices.Internal.BaseApi.Publisher.LoadPackageMetadata(String sdpFile)~~ at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetPublisher(String
sdpFile)~~ at Microsoft.SystemsManagementServer.WSUS.WSUSServer.PublishApplication(String sPackageId, String sSDPFile, String sCabFile) SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:35 PM 4168 (0x1048)
ERROR: Failed to publish sms client to WSUS, error = 0x80070003 SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:35 PM 4168 (0x1048)
STATMSG: ID=6613 SEV=E LEV=M SOURCE=»SMS Server» COMP=»SMS_WSUS_CONFIGURATION_MANAGER» SYS=confman.contoso.lan SITE=MON PID=1668 TID=4168 GMTDATE=Sat Dec 07 22:55:35.051 2013 ISTR0=»8427071A-DA80-48C3-97DE-C9C528F73A2D» ISTR1=»5.00.7958.1000″
ISTR2=»» ISTR3=»» ISTR4=»» ISTR5=»» ISTR6=»» ISTR7=»» ISTR8=»» ISTR9=»» NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:35 PM 4168 (0x1048)
Failed to publish client with error = 0x80070003 SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:35 PM 4168 (0x1048)
completed checking for client deployment SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:35 PM 4168 (0x1048)
HandleSMSClientPublication failed. SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:35 PM 4168 (0x1048)
Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:35 PM 4168 (0x1048)
Trigger event array index 0 ended. SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:35 PM 4168 (0x1048)
SCF change notification triggered. SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:40 PM 4168 (0x1048)
Populating config from SCF SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:40 PM 4168 (0x1048)
Waiting for changes for 58 minutes SMS_WSUS_CONFIGURATION_MANAGER 12/7/2013 5:55:40 PM 4168 (0x1048)
«When you hit a wrong note it’s the next note that makes it good or bad». Miles Davis