I have set an Azure Virtual Machine running Windows Server 2016 and now I need to install WCF RIA Services 1.0 SP2 on it.
Until Windows server 2012 I used to do that via command prompt:
msiexec /j RiaServices.msi SERVER=true
However in 2016 I receive the following message:
"You do not have sufficient privileges to complete the re-advertisement of this product. Re-advertisement requires initiation by a local system account calling the MsiAdvertiseScript API, such as through Group Policy Software Development."
Don't know what does it mean or how to make installation works. Obviously I am running command prompt as Administrator.
Any ideas?
I solved this problem changing the command line to:
msiexec /package RiaServices.msi SERVER=true
Still not sure exactly why, but the installation succeeded.
Related
Please consider the following error when trying to run the HL7 Accelerator Setup.exe executable.
I'm installing on a Windows Server 2012 R2 VM.
BizTalk 2013 is already installed and configured successfully using Global domain groups for BizTalk Server Administrators (and all other groups for that matter). I am a part of all groups.
SQL Server 2012 SP3 was installed prior to BizTalk
When I go to run the HL7 Accelerator MSI, I get the error pictured above, which states:
Error: Installation cannot be performed because the BizTalk server has not been configured or user account is not a member of the BizTalk Server Administrators group
Like I said, BizTalk is configured, the groups are Global and I'm a member, I'm also a local admin on the machine.
I've also tried this altered MSI from this post to no avail, I get the same error.
I'm at a loss. I can't find anything anywhere explicitly saying that any of these versions are incompatible, and I know SQL Server 2012 SP1 is compatible based on other installations we have running.
Could it be something with Windows Server 2012 R2? I don't know how I'd get this far and not be allowed to install the accelerator of all things.
I've 8 computers running Windows 8 (the basic edition) and I'm trying to run some application on each of them with a batch script.
I tried:
PsExec.exe -i -d -u USER -p PASSWD \\PCNAME explorer.exe
But it gives me:
PsExec v1.98 - Execute processes remotely
Copyright (C) 2001-2010 Mark Russinovich
Sysinternals - www.sysinternals.com
Couldn't access GATE1:
Access is denied.
It works fine on other PCs with Windows 7 Professional.
Does it works just on Pro edition? If so, is there a way I can run something remotely on Win 8?
I resolved the same PsExec "Access is Denied" error on a Windows 8 Pro 64-bit target machine with the following registry modification on the target machine:
Registry Location: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\System
Add DWORD LocalAccountTokenFilterPolicy
Set LocalAccountTokenFilterPolicy to 1
(Reboot)
In domain based environment, Microsoft PowerShell Remoting may be an alternative to PsExec.
In workgroup setup, especially among many different versions of Windows it may get bit challenging.
PowerShell remoting requires PowerShell 2.0 on both client and server.
Also, ssh with it's all capabilities (including launching remote commands) works under Windows, even free servers (freesshd) and clients (PuTTY family) are available . Downside is requirement for highly privileged account (usually, in some Administrators group) - at least for initial setup.
The GATE1 part in your log is interesting - PsExec requires so called "admin share" enabled (not sure does it work in Windows 8). I'd bet it's not the system, but a network issue.
I have made a WCF data service and a test client which both run fine on my local machine. The service is hosted on the local IIS on my machine.
Now I'm trying to setup a remote win 2008 R2 server to host the wcf data service, and this is where I run into trouble.
I have first tried to install "WCF Data Services 5.0 for OData V3" from http://www.microsoft.com/en-us/download/details.aspx?id=29306
But I get a "0x80070643 Fatal error during installation"-during installation. I have the log file if that helps.
Now I'm thinking, is it because I need to install "http://www.nuget.org/packages/Microsoft.Data.Services" on the server? I know I did this on my local machine. However this would require me to install Powershell, Visual Studio and NuGet on the server. Is this necessary to get things to work?
If you're using the NuGet packages in your project, then the easiest way is to bin-deploy the WCF DS runtime assemblies. More details here: http://blogs.msdn.com/b/astoriateam/archive/2012/08/29/odata-101-bin-deploying-wcf-data-services.aspx
Is there any possible way to create a setup in for my program written in vb.net using sql server as the backend.I have a module which creates the database code and i have also created a setup in vb.net for my project but i want this setup to run properly even in a system which doesnt have visual studio and sql server installed.I tried running it on a system which doesnt have both but the error i get is sql server 2005 doesn't allow remote connections in default settings,i tried changing some settings but nothing seems to work.Is it necessary for a server to be there for creating the database?
a little Google always does the trick...
To configure SQL Server 2005 to allow remote connections, you must complete these steps:
1.) Enable remote connections on the instance of SQL Server that you want to connect to from a remote computer.
2.)Turn on the SQL Server Browser service.
3.) Configure the firewall to allow network traffic that is related to SQL Server and to the SQL Server Browser service.
How To Configure Sql 2005 to allow Remote Connections
When I write programs that require SQL Server to be installed on the client, I use the following logic :
Determine if SQL Server is installed on the client machine
If it is not installed, I prompt the user to download it (or download it for them using your installer script. I use NSIS installer). Make sure to install the appropriate version for the user based on your requirements (and the client's operating system). I typically use SQL Sever 2008 R2 Express Edition, SP1.
I then execute the SQL installer using my installer script command. In NSIS, it's ExecWait. In VB.Net you have something like this. You'll have to install it via command line parameters. Here are the list of command line parameters: http://msdn.microsoft.com/en-us/library/ms144259(v=sql.100).aspx
Here's what I use:
C:\PathToMySQLDownload\SQLEXPR.exe /QUIETSIMPLE /SkipRules=RebootRequiredCheck
/ACTION=install /IACCEPTSQLSERVERLICENSETERMS=1 /FEATURES=SQL
/INSTANCENAME=MSSQLSERVER /SECURITYMODE=SQL /SAPWD=MySAPassword /NPENABLED=1
/TCPENABLED=1 /SQLSVCACCOUNT="NETWORK SERVICE" /SQLSYSADMINACCOUNTS="NETWORK SERVICE"
/AGTSVCACCOUNT="NETWORK SERVICE" /ASSVCACCOUNT="NETWORK SERVICE"
/RSSVCACCOUNT="NETWORK SERVICE" /ISSVCAccount="NETWORK SERVICE"
/ASSYSADMINACCOUNTS="NETWORK SERVICE
You can include SQL Server Express in the Pre-requisites for your setup project.
When you build the setup project, it will pick up the packages that are required for the installation from C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bootstrapper\Packages
You can then amend the package.xml file for SQL Express to change how it is configured by the installation. Look for the Command Arguments element, and then to switch on Mixed mode authentication add SECURITYMODE=SQL
to enable remote access add DISABLENETWORKPROTOCOLS=0
(or for SQL 2008 r2 it's /tcpenabled=1 )
When the end user runs the isntallation, SQL Express will be installed first, with the options you have specified.
We have an application that starts a WCF server and the app reads from it.
It starts and can be read fine on all Windows XP machines.
On our Vista machine, however, we get:
System.ServiceModel.AddressAccessDeniedException
"The process has no rights to this namespace."
System.Net.HttpListenerException
The URL is at localhost:
http://localhost:8731/ABC.Testing.Business.Core/SecurityService/?wsdl
The error message sent us here:
http://msdn.microsoft.com/en-us/library/ms733768.aspx
And we did what it said:
netsh http add urlacl url=... user=...
which changed the rights but the WCF service still cannot start on Vista.
Does anyone have any experience with this that could move us forward? Thanks.
I had a similar issue with Windows 7 running Visual Studio 2010. My solution was a simple WCF service library with a simple console project serving as the WCF service host.
My base address in app.config was "http://localhost:8080/BookService" and I forgot that I had to start Visual Studio as an administrator in order to get Windows to map that port to my app.
As soon as I started Visual Studio as an Administrator (right click, Run as administrator) it ran like a champ.
try reading through this blog post and see if it helps.
http://blogs.msdn.com/paulwh/archive/2007/05/04/addressaccessdeniedexception-http-could-not-register-url-http-8080.aspx
I was having the similar problem while running the Project in VS2013 on Windows 8 OS, this problem get solved when I started my project as administrator..
Try to start up your app as administrator.
Thanks
Mayank Nagar