winform Apps for SharePoint 可在开发人员上运行，但在暂存过程中出现错误
几分钟后我就明白了。
Visual Studio 即时调试器 winprogram.exe 中发生了未处理的 win32 异常[6108]
然后我在事件记录器中看到了这一点。 时间提供商 NtpClient：在 8 次尝试联系域控制器 dc.columbiauniv.gov 后，未收到来自域控制器 dc.columbiauniv.gov 的有效响应。该域控制器将被丢弃作为时间源，并且 NtpClient 将尝试发现新的域控制器以进行同步。
有关详细信息，请参阅帮助和支持中心：
I get this after few minutes.
visual studio just-in-time debugger an unhandled win32 exception occured in winprogram.exe[6108]
Then I see this in the event logger.
Time Provider NtpClient: No valid response has been received from domain controller dc.columbiauniv.gov after 8 attempts to contact it. This domain controller will be discarded as a time source and NtpClient will attempt to discover a new domain controller from which to synchronize.
For more information, see Help and Support Center at
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
看来这段代码适用于 Dev 和 Staging。
String strDT = DateTime.Now.ToString("yyyyMMddHHmmss");
我之前使用过这段代码，它只适用于开发人员。
String strDT = DateTime.Now.Year.ToString() + DateTime.Now.Month.ToString() + DateTime.Now.Day.ToString() + DateTime.Now.Hour.ToString() + DateTime.Now.Minute.ToString () + DateTime.Now.Second.ToString();
It seems that this code works on both Dev and Staging.
String strDT = DateTime.Now.ToString("yyyyMMddHHmmss");
I was using this code before and it only worked on Dev.
String strDT = DateTime.Now.Year.ToString() + DateTime.Now.Month.ToString() + DateTime.Now.Day.ToString() + DateTime.Now.Hour.ToString() + DateTime.Now.Minute.ToString() + DateTime.Now.Second.ToString();
我不太确定这与 Sharepoint 有什么关系，但无论如何...
我怀疑 NTP 错误是否相关 - 这些错误只是告诉您您的计算机无法看到域控制器，这可能是因为您与您的域控制器不在同一子网上
要追踪崩溃：
- 尝试在另一台安装了 Visual Studio 的计算机上运行该应用程序。如果出现错误，就在那里调试
- 添加追踪。您甚至可以让应用程序将跟踪日志写入控制台，以便您准确地找出代码中应用程序崩溃的位置。
当您发现错误时，请修复错误或添加 try/catch 块以适当地捕获和处理异常
I'm not quite sure what this has to do with Sharepoint, but regardless...
I doubt the NTP errors are related - those errors are just telling you that your computer can't see the domain controller, which is likely caused because you aren't on the same subnet as your domain controller
To track down the crash:
- Try to run the application on another computer that has visual studio installed. If the error comes up, debug it there
- Add in tracing. You could even have your application write trace logs to the console so that you find out exactly where in your code the application is dying.
When you find the error, either fix the bug or add in a try/catch block to catch and handle the exception appropriately