partially trusted reading app.config on Windows 7 in network share - windows-7

I'm getting this error in Windows 7 64 bits:
An error occurred creating the configuration section handler for '': That assembly does not allow partially trusted callers.
This happens when I try to read a config section, the section is mapped to a class that is in a DLL in the GAC, I'm using Visual Studio 2010 targeting the framework 3.5, I'm in a domain and the exe is running from a network share, the exe is signed.
This is failing only on Windows 7, an XP Machine can run the app just fine from the same network share, I'm using my domain account on both machines.
Does anyone know why this is failing on Windows 7?, thanks a lot for your time.

Having bumped into similar trouble when our IT department did a stealth upgrade of users' machines to Windows 7, I suspect you may need to update the trust level with caspol.exe
For XP we would normally run:
%windir%\Microsoft.NET\Framework\v2.0.50727\CasPol.exe -q -m -ag 1.2 -url file:\\s:\* FullTrust
but now with Win7 it has changed to:
%windir%\Microsoft.NET\Framework64\v2.0.50727\CasPol.exe -q -m -ag 1.2 -url file:\\s:\* FullTrust

I Fixed using this command:
caspol -cg 1.2 FullTrust
The Intranet Zone had the LocalIntranet permissions set, (don't know why it was LocalIntranet, it should be FullTrust).
Thanks to dreynold.

Related

I can't connect to Mac with Xamarin Mac Agent from Visual Studio 2015

I'm continuing my adventure with Xamarin.
I'm developing an Xamarin Forms application with a Portable Class Libraries (PCL).
I have compiled and debugged my application by Android, but now, I'm interested to run the application in iOS to test in this platform.
I have a problem with the connection between my PC and the Mac.
I have a PC (Windows 8.1) with Visual Studio Community 2015 with Xamarin tools installed.
In my Mac Mini, I have installed OS X (v10.11.3), XCode (v7.2) and Xamarin Studio. I have logged in with my Xamarin account.
In the two machines I have the same Xamarin version.
I have followed the Xamarin walkthrough.
On Visual Studio I open the Xamarin Mac Agent. It finds my Mac Mini. Then it asks me the Mac credentials (user and password).
The login works at this point.
Then, in the solution, I set the iOS project as the startup project. I clean the solution, I build again and start the compile/debug process (F5).
In this point, the output retrieves a message:
1> Connecting to Mac server Macs-Mac-mini.local...
1>C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Windows.After.targets(54,5): warning : Could not authenticate the user using the existing ssh keys
1>C:\Program Files (x86)\MSBuild\Xamarin\iOS\Xamarin.iOS.Windows.After.targets(54,5): error : Unable to connect to Address='Macs-Mac-mini.local' with User='macmini
I have used Putty (SSH Client) to check with my user/password if I'm able to connect to Mac, and I have had success.
Into /Users/macmini2/.ssh/authorized_keys file (Mac machine) each time that I use the Xamarin Mac Agent, Visual Studio adds a new key entry (it adds the same repeated).
I see that perhaps the problem is related with ssh keys.
Why I have this problem? What am I doing wrong?
A thing that I have tested was openning the Xamarin project directly in Mac with Xamarin Studio, build it and run the simulator. It works.
I have seen other similar question, but I think that it doesn't have the same problem.
EDIT:
More specific information about the error when I try to compile/debug:
Could not authenticate the user using the existing ssh keys
Xamarin.Messaging.VisualStudio.MessagingAuthenticationException: Could not authenticate the user using the existing ssh keys ---> Renci.SshNet.Common.SshAuthenticationException: Permission denied (publickey).
en Renci.SshNet.ClientAuthentication.Authenticate(IConnectionInfoInternal connectionInfo, ISession session)
en Renci.SshNet.ConnectionInfo.Authenticate(ISession session)
en Renci.SshNet.Session.Connect()
en Renci.SshNet.BaseClient.Connect()
en Xamarin.Messaging.VisualStudio.MessagingService.<ConnectAsync>d__70.MoveNext()
--- Fin del seguimiento de la pila de la excepción interna ---
EDIT 2:
I have revised the troubleshooting Xamarin page, specifically that it says "Unable to authenticate with SSH keys. Please try to log in with credentials first".
I have run:
chmod og-w "$HOME"
grep sshd /var/log/system.log > "$HOME/Desktop/sshd.log"
cd Desktop
cat sshd.log
And the content of the file is:
Apr 18 09:23:28 Macs-Mac-mini sshd[769]: Authentication refused: bad ownership or modes for directory /Users/macmini2/.ssh
Apr 18 09:25:27 Macs-Mac-mini com.apple.xpc.launchd[1] (com.openssh.sshd.EE9A94ED-????-....-????-77254934B300[769]): Service exited with abnormal code: 1
Apr 18 09:59:39 Macs-Mac-mini sshd[1036]: Accepted keyboard-interactive/pam for macmini2 from 192.168.54.14 port 60413 ssh2
Apr 18 09:59:39 Macs-Mac-mini sshd: macmini2 [priv][1036]: USER_PROCESS: 1040 ttys000
But now I don't know what I have to do to solve it.
You have to try delete everything from
%localappdata%\Xamarin\MonoTouch
It helped me, I had the same (or similar) problem today.
I have found the solution about my problem. I have done the following steps:
In my Windows: I have removed the content from "%localappdata%\Xamarin\MonoTouch."
In Mac terminal: Remove the authorized_keys Mac file ("rm /Users/macmini2/.ssh/authorized_keys" in my case)
In Mac terminal: chmod g-w /Users/macmini2/
In Mac terminal: chmod 700 /Users/macmini2/.ssh/
In Mac terminal: Create a empty file: /Users/macmini2/.ssh/authorized_keys (with vim, for example)
In Mac terminal: chmod 600 /Users/macmini2/.ssh/authorized_keys
On Visual Studio: Login with Xamarin Mac Agent
On Visual Studio: Run the application with [Debug] - [iPhoneSimulator] - [iPhone 5 iOS 8.1]
And finally, the simulator runs on Mac computer.
This link helped me.
Xamarin has a Troubleshooting page with large focus on SSH issues:
Connection Troubleshooting
Specifically these two:
Log File Location
Mac – ~/Library/Logs/Xamarin-[MAJOR.MINOR]
Windows – %LOCALAPPDATA%\Xamarin\Logs
The log files can be located by browsing to Help > Xamarin > Zip Logs in Visual Studio.
"Unable to authenticate with SSH keys. Please try to log in with credentials first"
Known cause:
SSH security restriction – This message most often means that one of the files or directories in the fully qualified path of $HOME/.ssh/authorized_keys on the Mac has write permissions enabled for other or group members. Common fix: Run chmod og-w "$HOME" in a Terminal command prompt on the Mac. For details about which particular file or directory is causing the problem, run grep sshd /var/log/system.log > "$HOME/Desktop/sshd.log" in Terminal, and then open the sshd.log file from your Desktop and look for "Authentication refused: bad ownership or modes".
Furthermore there is this section, which does not directly match the error you are seeing but goes into some detail on SSH configuration and diagnosis:
"Couldn't connect to MacBuildHost.local. Please try again."
Reported causes:
Bug – A few users have seen this error message when attempting to log in to the build host using an Active Directory domain user account.
Bug – Some users have seen this error when attempting to connect to the build host by double-clicking the name of the Mac in the connection dialog. Possible workaround: Manually add the Mac using the IP address.
Bug #35971 – Some users have run across this error when using a wireless network connection between the Mac build host and Windows. Possible workaround: Move both computers to a wired network connection.
Bug #36642 – On Xamarin 4.0, this message will appear anytime the $HOME/.bashrc file on the Mac contains an error. (Starting with Xamarin 4.1, errors in the .bashrc file will no longer affect the connection process.) Workaround: Move the .bashrc file to a backup location (or delete it if you know you don't need it).
Limitation – This error can appear if the Mac build host is connected to a router that has no access to the internet (or if the Mac is using a DNS server that times out when asked for the reverse-DNS lookup of the Windows computer). Visual Studio will take roughly 30 seconds to retrieve the SSH fingerprint and eventually fail to connect.
Possible workaround: Add "UseDNS no" to the sshd_config file. Be sure to read about this SSH setting before changing it. See for example http://unix.stackexchange.com/questions/56941/what-is-the-point-of-sshd-usedns-option.
The following steps describe one way to change the setting. You will need to be logged in to an administrator account on the Mac to complete the steps.
Confirm the location of the sshd_config file by running ls /etc/ssh/sshd_config and ls /etc/sshd_config in a Terminal command prompt. For all of the remaining steps, be sure to use the location that does not return "No such file or directory".
Run cp /etc/ssh/sshd_config "$HOME/Desktop/" in Terminal to copy the file to your desktop.
Open the file from your Desktop in a text editor. For example you can run open -a TextEdit "$HOME/Desktop/sshd_config" in Terminal.
Add the following line at the bottom of the file:
UseDNS no
Remove any lines that say UseDNS yes to make sure the new setting takes effect.
Save the file.
Run sudo cp "$HOME/Desktop/sshd_config" /etc/ssh/sshd_config in Terminal to copy the edited file back into place. Enter your password if prompted.
Disable and re-enable Remote Login under System Preferences > Sharing > Remote Login to restart the SSH server.
I have just solved this problem!
It was nonsense.
To connect Visual Studio Xamarin project and simulate that on Mac when you get:
Couldn't connect to computername.local please try again later.
What you need to do next:
Follow the solution from xamarin community about mac connection
after this point if everything OK, you will connect, but if no..
Install XAMARIN STUDIO on MAC. After installation start XAMARIN studio, create your own app and run with simulator
Close app and try to connect again from Windows computer.
At this point you will make synchronization and that's all.
Problem solved! I hope this will be useful for somebody.
For me helped next solution:
1)On Windows open Visual Studio:
Tools=>Options=>Xamarin=>Other and click in Check Now
2)On Mac open Xamarin Studio Community (https://www.xamarin.com/download)
Xamarin Studio Community=>Check for Updates... (and download last one)
After updates all works fine.
I tried a few of the solutions mentioned here and had no success.
However (though not ideal) if I run Visual Studio in Administrator Mode I can successfully connect. Could be a work around for some until a better solution is found.
This is not perfect solution, but made success in my case
Your mac account should not contain any special characters- This is limitation in connection to mac from windows
company-mac1 --- wrong
comapanymac1 --- Correct
For what it's worth I just solved this issue by checking the logs as noted above and in the Xamarin Troubleshooting docs. It turned out to be mismatched iOS versions. Once I updated the Mac version it worked.
In my case, i installed mono sdk on my mac it solve the problem
http://www.mono-project.com/download/#download-mac
Ignored the agent that Visual Studio wizard showed. Something about the Mac computer name VS didn't understand.
I did 'Add Mac', used the IP address, then it connected. That was annoying.
Did you turn on remote login and that is the user/login that is currently logged into the machine? Also, have you tried connecting directly to the IP address instead of the DNS name?
I am on a client's network (different domain than mine) and my VS would never connect via the computer name. I always had to type in the IP address. Also, watch the out put for "Xamarin" in the Output panel/window and see if it gives any more helpful information.
I had this problem recently (despite having enabled Sharing on the OSX host and checking firewall) and it turned out that both OSX Machine and Windows Machine needed the exact same version of Xamarin.iOS and a restart.
Updating both, restarting both, solved the problem for me.
I think what fixed it for me was opening git bash then running ssh onto the mac box. After saying Y to trusting credentials it worked.
In my case I could not connect to XCode because "XCode" file wasn't located at the "Application" folder on MacOS. When the "XCode" app was moved to "Application" folder, I had connect.
Update Visual Studion on Mac and:
1) Delete on Mac - all files in .ssh (rm *)
2) Delete on Mac the folder .ssh
3) On Windows, generate your ssh key and transfer to MAC - for that Open Windows PowerShell and execute the follow commands:
[generate the key]
PS>ssh-keygen -t rsa -b 4096
[define the remote host variable]
PS>$REMOTEHOST="name_of_mac_user#ip_mac_machine"
[send the key to mac machine]
PS>scp "$env:USERPROFILE\.ssh\id_rsa.pub" "${REMOTEHOST}:~/tmp.pub"
[copy the key tmb.pub to authorized_keys file and set the permissions]
PS>ssh "$REMOTEHOST" "mkdir -p ~/.ssh && chmod 700 ~/.ssh && cat ~/tmp.pub >> ~/.ssh/authorized_keys && chmod 600 ~/.ssh/authorized_keys && rm -f ~/tmp.pub"
4) check on mac .ssh folder if the authorized_keys file is correct:
tail ./authorized_keys
5) check the permission for authorized_keys (-rw-------)
ls -al ./authorized_keys

MPICH2 error - Credentials for <user> rejected connecting to <host> Aborting: Unable to connect to <host>

I need to get MPICH2 working for my college project. But it appears I won't implement anything until I manage how to start MPICH2. For now I only try to run anything on my computer, nothing more. What I do:
I install the MPICH2 (from mpich.org/downloads, from the bottom of the site - the x86_64 Windows version) on my 64bit Windows 7 (I also tried the same with my 64bit Windows 8). I start the installer from a command line (run as an administrator), install MPICH2 for everybody (although my acc is the only one). After successful installation I run the wmpiregister.exe, where I type Danioss (it's the name of my account) and the password for this account. I click register, everything seems to be fine so far. Then I run wmpiconfig.exe, I don't change nor click anything and there is this error:
'g-pc: MPICH2 not installed or unable to query the host'
I can see on the left the table with my host name (g-pc) and the version of MPICH - 1.4.1p1. So it sees it is installed here but cannot query the host. I have no idea what that means.
Of course I tried to execute any compiled program but after running wmpiexec.exe, choosing the file and clicking Execute - I get
'Credentials for Danioss rejected connecting to g-PC
Aborting: Unable to connect to g-PC'
I tried running every .exe as an administrator, didn't help. I also installed and reinstalled the whole MPICH2 tens of times (literally - tens) trying different configurations. I also tried to install the 32bit version but that made no progress. I really have no idea what the problem is.
Please, help me!
Greetings,
Daniel
Try not specifying username after running wmpiexec -register. Just password for your current user. That worked well for me. Source: https://trac.mpich.org/projects/mpich/ticket/1151
First: crate a windows user password of your windows user acount
Second: go to installdir deform (C:\Program Files\SFTC\DEFORM\v10.2\3D)
Third: execute "wmpiregister.exe" and register user name and password that your windows user name and password
start deform on multiprocessor
good work
You need to run wmpiregister.exe which is in bin folder, to register your Windows user.
Register using mpiexec -register with ".\" before the username, in your case: .\Danioss.

VS 2013 kernel-mode driver debugging

I'm trying to set up kernel debugging with VS 2013. When I go to Drivers/Add to add a new target machine, it connects to the remote computer and runs through a lot of setup, but it there are always 2 commands that fail.
I looked up the command that is failing in the log and I pasted it into a batch file and ran it on the target machine. I runs just fine. But then when I try to rerun Add Computer from VS, I get the same failure.
RemoteExecute: Binary: $KitRoot$\Testing\Runtimes\TAEF\te.exe
RemoteExecution: Arguments:
"%SystemDrive%\DriverTest\Run\DriverTestTasks.dll"
/select:"#Name='DriverTestTasks::_ConfigureKernelDebugger'"
/p:"DebugTransport=NET" /p:"NetHost=192.168.1.109" /p:"NetPort=50015"
/p:"NetKey=8XD3HYLMVI0D.RKFEA2BPIXO.27JOLNYURED5.MV9OGRF4XR9V"
/p:"StartPolicy=Active" /p:"IgnoreUserModeExceptions=0"
/p:"SuppressReboot=1"
/rebootStateFile:%SystemDrive%\DriverTest\Logs\DriverTestReboot.xml
/enableWttLogging
/wttDeviceString:$LogFile:file="%SystemDrive%\DriverTest\Logs\Configure_debugger_settings_(x86)_(possible_reboot)_00007.wtl",writemode=append,encoding=unicode,nofscache=true,EnableLvl="WexStartTest|WexEndTest|WexXml|WexProperty|WexCreateContext|WexCloseContext|*"
/runas:Elevated RemoteExecute: Process creation return code: 0
RemoteExecute: Process exit code: 0 Initialize: Computer: w8x86wdk-hp
Result completed Test process exit code: -1
I have tried this both with a VMware VM target and against a physical PC target and I have tried adding the computer in the reverse direction and I always get the same failures. I can ping these machines from each other and all machines are Win8 x86. Network discovery and sharing are on. The Windows firewalls are off. These are virgin OS installations so there's nothing on the machines except the OS, VS2013, and WDK 8.1.
Any tips on how to resolve this?
Had same issue when used ws2012 for TARGET machine.
When installed WIN81 instead, turned off UAC and DID NOT install wdk on TARGET - everything started working. Read carefully how to PROVISION TARGET. (it says: dont' install WDK there:)
HOST and TARGET was in the same home workgroup with same passwords for Administrator and MyUserAcc.
also:
under HKCU\Software\Microsoft\Windows\CurrentVersion\Policies\System set EnableLUA=0
I am just testing it so I think you should first check your target computer security issue. Then set your port pipe connection and your network adapter setting in your virtual pc.
After that setting make your computer configuration then works perfectly.

Can't start Portal Express 7 on Windows 2003

I have a Windows 2003 SP2 Virtual Box guest in which I'm trying to install Portal Express 7.
During the installation there's a prompt that said that the Server couldn't start and I have to that manually. When I try to start it using startServer.bat I get every time this message:
ADMU3011E: Server launched but failed initialization. startServer.log,SytemOut.log(or job log in zOS) and other log files under C:\IBM\WebSphere\AppServer/profiles\default\logs\server1 should contain failure information.
ADMU7704E: Failed while trying to start the Windows Service associated with server: WebSphere_Portal;probable error executing WASService.exe: com.ibm.ws.management.tools.ProblemInWASServiceException: ADMU7711E: Unexpected exception associated with WASService.exe: exitCode = -1 during processing of server with name: WebSphere_Portal
In the logs I only found java.lang.NoClassDefFoundError:com/ibm/ffdc/impl/EmptyProvider$EmptyFfdc and several verbosegc.txt files. Have anyone succeeded in installing IBM WP 7 on Windows 2003?
PS: My problem is very similar to this DeveloperWorks post.
If you can start it manually but not through Windows Service, perhaps something got corrupted into the service definition. No problem, you may very simply remove it (WASService.exe -remove servicename in AppServer/bin directory ), and then add it again
I use a syntax like this one
wasservice -add "Cluster1_server1" -serverName "Cluster1_server1" -profilePath "D:\IBM\WebSphere\AppServer\profiles\AppSrv01" -wasHome "D:\IBM\WebSphere\AppServer" -stopArgs " -username youradmin-password yourpassword" -encodeParams
or you may also insert username and password into soap.client.props, so you don't need to change it all the times.

Windows Server 2008 Cdonts issue

Cdonts is not working in server 2008 (im using 32bit)
i tried copying cdonts.dll to windows/system32 folder
did regsvr32
it failed
any alternatives?
-Vivek
This is probably because you have the 64-bit version. You have to put cdonts.dll in the windows\SysWOW64 folder and then run
regsvr32 C:\Windows\SysWOW64\cdonts.dll
You will also have to edit the application pool of your site and set "Enable 32-bit Applications" to True.
Someone seems to have successfully installed CDONTS on Windows 2008 x64 on IISLogs.com. I did not try myself though.
Here his procedure :
Copy CDONTS.dll from another server to C:\Windows\SysWOW64
Run regsvr32 c:\windows\SysWOW64\cdonts.dll
Grant the appropriate permissions on C:\inetpub\mailroot\pickup (I granted USERS group Modify permissions). You could get permission denied if the folder security isn't adjusted.
I'm assuming you have installed the SMTP Service located in Server Manager > Features > SMTP Server option
Make sure when you when you install the SMTP service, you enable Relay for localhost > Administrative Tools > Internet Information Services (IIS6) > SMTP Virtual Server > Right click, Properties > Access Tab > Relay button > Add 127.0.0.1 in the option. Also enable logging for additional troubleshooting.
CDONTS is deprecated (around the time of XP, I believe?)
Here are 2 common replacements.
http://www.w3schools.com/asp/asp_send_email.asp
http://www.aspcode.net/ASPMail-SMTPsvgMailer-.aspx

Resources