I have this bizarre scenario happened to me today morning. I was scheduled to publish a new version of my application and I did it successfully (as Visual Studio 2012 output said!). The Publish HTML also had the correct version in it.
Note
- Development Terminal runs on Windows 7 SP1 with Visual Studio 2012 Update 4,
Crystal Reports 13 for Visual Studio and Kaspersky EndPoint Security 10 for Windows;
- Files are copied over a FTP to a Windows Server 2003 server within the LAN;
- User Terminals are loaded with Windows 7 SP1 and Windows XP SP3 with Kaspersky EndPoint Security 10 for Windows;
When I checked with Users, some said new release weren't applied in their terminals. Further investigation revealed that those whom had Windows XP, had itself updated with the latest release, where as those whom had Windows 7 did not detect any updates available and runs the previous released version when ran without any errors.
Further, I noted that in Users who were having Windows 7, if the Application is Run from Start-up menu it loads the previous release which had been there earlier. I tried uninstalling and deleted all contents in
C:\Users\\AppData\Local\Apps\2.0*
and launched the application from Publish.html web page again. Then I noticed that it prompts for installation and when I clicked "OK" it only installs an application with 6.95MB where as the new application is 7MB+. This proves that ClickOnce picks the previous release from some where, which I cant figure the location. I even tried up increasing the Publish Version thinking it will detect a signature change but did not. :(
I have checked the Manifest file in the server, it had the latest version specifying in it.
Let me know of any location where I could further investigate; I mean where does ClickOnce stores all files other than C:\Users\\AppData\Local\Apps\2.0* and where I could find the Log file which ClickOnce creates which I'm struggling to find
I have published releases earlier, but this is the first time I'm getting such problems. Since my last release which I publish, I had only installed Update 4 for Visual Studio.
Did anyone come across it?
These were my Settings:
Everything worked today morning. It seems, some client level cache was a reason to this problem in Windows 7 users.
Should I have urged the users to re-start their machine, this would have not caused; I presume. But nevertheless happy that everything went on board with the new update.
Related
Recently I updated my Windows from 8 to 10 and suddenly my SQL Server 2014 stopped working. When I open the Management Studio and try to connect to the Server (local) i obtain the following error:
Does any of you had similar problems? Before updating the Windows everything was running just fine.
I had the same problem after upgrading from Windows 8.1 Pro to Windows 10 Pro. I was able to resolve it as follow:
Control Panel
Administrative Tools
Services
The SQL Service Browser was Disabled
Right click and select Properties
Change the Startup type to Automatic (Delayed Start)
Click to Start button to start the service
And off you go. This should resolve the issue.
I just had the same issue after upgrading my laptop from Windows 8.1 to Windows 10; however, my solution was slightly different to the one suggested already, I had to:
1) Control Panel
2) Services
3) Right-click, Start, SQL Server service
I had to do this for all the SQL versions I have installed (08R2 up to 14). Somehow the upgrade stopped and didn't restart the SQL service.
I also encountered the same issue upgrading from Windows 7. First thing I did was open the SQL SERVER MANAGER CONSOLE and ensure that the server was still running. After seeing that it was, I restarted it, and that fixed the problem.
I personally would try these simple steps first... never know could be that easy.
Side note - if you have trouble finding the SQL Manager Console in your Programs list like I did, you can likely find it in your C:Windows/SysWOW folder (open file named SQLServerMananger##.msc).
I have published my winforms client application with click once.
I am using visual studio 8 and OS Win Server 2003 SP2.
first using click once i was not able to use excel upload part of my app in windows 7 (64) but it was working on server 2003(32)/2008(64) and windows 8(32bit).
but after some googling I had some suggestions which i have changed.
List of changes I have done
changed the OLEDB connection string to Provider=Microsoft.ACE.OLEDB.12.0;Data Source='".
changed the target platform to X86.
removed all the office components from the server and re-installed AccessDatabaseEngine.exe.
Checked the MIME type all the .deploy manifest and all are
there(also checked the office extensions).
After doing these changes I was able to use the Excel upload on all the OS.
But after 3 versions now its again stopped working.
Now I am out of clues what went wrong.
I have a Windows Forms application that I am using ClickOnce deployment for and everything publishes fine when I am attempting to publish in Windows XP. When I try the same publish feature in Windows 7, it hangs on the publish step.
I am using a UNC path (file share) to the server (Windows Server 2008 R2 with IIS 7). Why might this happen?
I never receive an error message and the process cannot be cancelled. I have to force-close Visual Studio and restart my Windows 7 PC because Visual Studio has some of the files locked.
UPDATE:
I was able to set full-control permission on the folder on the destination server for my domain PC, and I was then able to publish once. Then, every subsequent deploy hanged. I did notice however that it always hangs when it's trying to copy the Office Interop files. Why would this be?
UPDATE (2):
This is definitely related to the Office 2010 PIA files. Why would it not publish them? Again, this works flawlessly on Windows XP, but when I perform the deployment on Windows 7, the PIAs are not published.
It could be a UAC issue. Try running Visual Studio as an administrator when you do a publish.
When I run my application (WPF,VB.net 2008) on Windows XP, I get weird Windows Errors. When I installed VS2008 on the machines that got the error and debug. I got a loader lock exception, so I went into Debug and removed it. However, I still get the error when it is installed on the machine.
Is there a way to remove the Loader Lock Exception when the application is install. I do understands that it might not be the best solution, but it seems this happen only when I start an WindowsElementHost with a ReportViewer and this is causing the problem, so I don't really know what else to do with it.
All version of XP have that problem, as with 2003.
In Windows 7 and Vista I never run into that error while debugging and the installed product. The same thing applies with 2008 and 2008R2.
I've done a little bit of research and below you can find my guesses:
maybe it's a bug in the Report Viewer control itself and you should update to a later version. I've noticed that on December 2012 a new version was released (see this post), supposedly running on both .NET 3.5 and 4.0 (so it should work with VB 2008, see download page);
I've noticed that Report Viewer 2008 SP1 requires .NET 3.5 SP1 (see the download page) -- maybe an outdated version can trigger the exception you are seeing;
maybe Windows XP is not updated to the latest Service Pack or is the wrong edition -- again Report Viewer 2010 SP1 requires Windows XP SP3 (see download page) and Report Viewer 2012 does not run on Windows XP Starter Edition;
maybe it's a library used by Report Viewer that causes this exception (especially a mixed mode assembly) -- a dump or a stack trace would be helpful in this sense;
there is a comprehensive answer in this thread in the Visual Studio Tools for Office forum that lists several resources to understand this problem;
the previous link suggests that in some conditions it's safe to ignore this lock. If from your testing under Visual Studio with Loader Lock MDA disabled you see that there is no problem, you can disable the MDA in production machines using the instructions in this blog post -- basically it involves setting an environment variable and adding some lines to the app.config file (see also the documentation for Loader Lock MDA to see what the new lines should look like). I haven't tried it but I thought it may be useful for you as a last resort solution -- just be sure to test thoroughly your application to avoid undesired side effects.
To get more help, I suggest you so specify:
the version of Report Viewer you are using;
the version of .NET Framework you are targeting (in particular including Service Pack);
what Service Pack is installed for Windows XP;
any stack trace or debugging information you can gather.
I am trying to install SQL Server 2008 Developer Edition x64 on a Windows Server 2008 VM. I run the installer for a standalone installation and this works fine for the setup support rules bit. That passes ok but then I get this error:
TITLE: SQL Server Setup failure.
SQL Server Setup has encountered the following error:
Invoke or BeginInvoke cannot be called on a control until the window handle has been created..
BUTTONS:
OK
How can I resolve this? I am getting 2008 R2 CTP but this is just a CTP. My download is from DreamSpark.
Thanks
This isn't really a real solution, but it worked for me after the 5th attempt. Not sure if it makes a difference, but on the 5th attempt I minimized all other windows (so that SQL setup is the only window that has focus) since the issue appears to be UI related.
Update: After overcoming the 1st issue, I got another issue where the actual database engine component failed to install without reason. The solution was to restart and try again.
The x64 installer seems to be really buggy.
I've did another trick:
In the Installation Disc you will find a folder, x86 and x64
Select as per your OS and go inside the folder
Click on the LandingPage.exe
It will show the page, in that click on the second Option on the left hand menu "Installation"
Click on "Start Standalone installation from the menu at the right side
It will ask for the location files on the disc
Show the location,
e.g. <Your Disc Drive>/SQL Server Enterprise 2008/x86
It will complete the installation successfully
I see MS has answered this. It's because the release of MSSSQL is newer than the SP is. They have a hotfix that apparently needs application. Oh joy!
http://support.microsoft.com/kb/975055
You then have to request the Hotfix, and wait for the link to be sent to you. They say 5 minutes, but we'll see.
In Windows 7 64 Bit, press ctrl+alt+delete, start the task manager and end the landing page process and it will successfully install.
I had this same error a number of times trying to install SQL Express 2008 x64 on a 2008 R2 64-bit server (VMWare) and I finally got it working doing the following:
Start the installation and when it gets to the point where the security window pops up asking you if you authorize the installation to run, open the temp folder. C:{GUID} and copy that folder (contains setup.exe and supporting files) to your desktop.
Click "OK" on the security dialog and it will probably error.
Once the error dialog goes away just run the setup.exe from the temporary directory on your desktop and it works.
Hope this helps someone else.
~Matt Heidenreich
I had the same problem when i was installing on Window 7. The only thing I could find was to retry the install again right after the failure and it worked after some time.
Had the same problem; made sure no other instance of setup was running from process explorer and then restarted installation and it worked fine for me
Before Installation, close all windows explorer and web browser. :)
.
I had the same problem once with installing the service pack. The only thing I could find was to retry the install again right after the failure. It took about five times, but it eventually worked. I think there's something odd about the installer on 64-bit Windows.
closing all open windows worked for me. definitely a UI problem with 64 bit.
For Server 2003 with this issue, I installed 2008 R2 management tools - which should work fine with 2008.
http://www.microsoft.com/en-us/download/details.aspx?id=22985
Note: Needs PowerShell on 2003 to install: http://www.microsoft.com/en-us/download/details.aspx?id=20020