I have a MS Access 2003 Database which uses the command "CommonDialog".
In this Database has access many computers with windows 10 and Microsoft 365.
Some computers can work with no issue but some other appear the error:
"Object doen't support this property or method"
Do you know if there are any computer settings that can explain this behavior?
Microsoft has restricted the support of CommonDialog from Windows 10, build 1809 on.
You must switch to the FileDialog property. Unfortunately, you will need Access 2007 for it. Here is how to use the FileDialog:
https://support.microsoft.com/en-us/office/filedialog-property-8510b02d-e455-44a9-bf38-3787e6d5c8c1?ui=en-us&rs=en-us&ad=us
Related
I have installed ADLDS in my Windows 10 (21H2) machine, we don't have any domain controller, the idea is to use AD LDS for user management in our Plant SCADA application. I am trying to create an OU via powershell cmdlets. But i get the following error:
New-ADOrganizationalUnit : Unable to contact the server. This may be because this server does not exist, it is currently down, or it does not have the Active Directory Web Services running.
The same powershell cmdlets works fine with AD LDS instance installed in a server 2019. But i get issues when i run same powershell cmdlets in my windows 10 machine. When i checked the Server 2019 i can see there is a windows service "ADWS" running, but i don't find this in my windows 10 machine, so i am not sure if this is the issue as said in the error. i installed the RSAT:ADLS tools from optional feature, so couldn't figure out how to get this feature(ADWS) and get my cmdlets work in my windows 10 machine. ( i am able to create OU via ADSI edit, but the idea is we want to use powershell to automate) i would really appreciate if some one could shed somelight on this ( all my google search results are leading me nowhere :( )
A customer of ours is using a kind of sharepoint (not sharepoint) -a document repository- that, for what I saw, uses webdav.
There are two terminal servers, one of them is Windows 2008 R2 Datacenter v6.1 build 7601, Office 2016, and Internet Explorer 10.0.9200.17609IS. They couldn't access anything at all, they went as far clicking "edit" on the site and then Word they that he's sorry because he couldn't open the document.
I've fixed that, I added the site to the Trusted Sites list, and disabled SSL 3.0 and TLS 1.0. Local admins can open and update documents. Non admin users can open the document but not update it, and by can't I mean that Word opens the document in read-only mode and any attempt to switch to read-write will save the document in the local computer.
Now, the other server, Windows Server 2012 R2 version 6.3 build 9600, Internet Explorer 11.0.9600.19867, the former fix did the trick for both admins and non-admins.
Does anyone know where to look?
Thanks,
Max
Trying to deploy some software that uses AppFabric in IIS. Yes, I already know AppFabric is deprecated; I didn't architect this software, so don't look at me! I also have the CU7 update for AppFabric installed.
I'm on Windows Server 2016 with IIS 10. No matter what I click on involving AppFabric in IIS, I get an error: The method or operation is not implemented.
Opening up the Event logs, I see that the method in question is a PowerShell commandlet: error running cmdlet 'out-lineoutput'. The method or operation is not implemented.
Out-LineOutput allegedly was introduced in PowerShell 5, and I've read that it only exists in regular PowerShell (not ISE). Beyond that, I haven't found any reference to that commandlet in regards to AppFabric.
What's driving me extra nuts is that I have a sandbox machine, also running Server 2016, where everything is working OK. I have confirmed that:
the PSModulePath environment variable is the same on both; and
running Get-Module at a Powershell prompt shows the same modules installed on both.
I've tried uninstalling/reinstalling AppFabric and the CU7 patch, adding my Application Pool Identity(ies) to the AS_Administrators group . . . nothing is working. Help me, Stack Overflow!
It turned out this was due to a registry key entry setting logging. In regedit, go to
HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\PowerShell\Transcription
Check out the EnableTranscripting property. If this is a 1, change it to a 0.
I tried about a dozen PowerShell scripts that I found and not one even created a single share.
We are migrating from Win 2008 and SQL Server 2008 R2 to Windows 2012 and SQL Server 2014.
I have to create a ton of shares and assign a lot of varying permissions.
I'm looking for (ideally) a Powershell script (but can live with VB or anything else) that can go through a list of shares and permissions and create/assign them.
For example
E:\Folder1\A Share1 Domain\Tom Read
E:\Folder1\A Share1 Domain\Dick Full
E:\Folder1\A Share1 Domain\Harry Change
So it would go through every line, see if the share exists, if not create it, then assign the permissions.
On Server 2012R2 you can use the New-SmbShare cmdlet : https://technet.microsoft.com/en-us/library/jj635722(v=wps.630).aspx
On older versions you have to fall back to WMI to do it :https://msdn.microsoft.com/en-us/library/aa389393(v=vs.85).aspx (the article even has a PS example).
With Set-Acl you can set the ACLs for the shares.
As you can see all the tools to acomplish this are available in a default installation of Windows Server.
Our Global company is in the process of rolling out office 365 for the whole group. currently i am the only user in my location to start using office 365. I can create a new outlook 2013 profile for the office 365 account and it works well. Problem i'm having is after launching the new Office 365 profile outlook keeps prompting me for my local windows username and password. this only happens when i'm connecting to my local network. Our local exchange server is still in production and cant be removed at this stage as all my other 400+ users use it.
If i connect to my office 365 profile in outlook from another network this does not happen.
I created a new profile for outlook 2013 and this still occurs.
If i enter my credentials in outlook 2013 it downloads my local OAB instead of using the new Office 365 address book.
Current setup: Local Exchange 2007 server.
Office 2013 on windows 7 64bit
Microsoft employee here - sorry to hear about the difficulties you're having!
Can you answer these questions for me:
1. What specific Outlook 2013 version are you using? e.g. 15.0.4631.1000
2. Does the problem still occur if you set the ExcludeScpLookup Autodiscover reg value? Steps to do so can be found below:
a. Start regedit
b. Select reg key HKEY_CURRENT_USER\Software\Microsoft\Office\15.0\Outlook\AutoDiscover
c. Create a new DWORD value in this AutoDiscover reg key named "ExcludeScpLookup" (no quotes) with value 1
d. Restart Outlook and boot into your O365 profile
Note that #2 is not a permanent solution, just a troubleshooting step to determine where the issue might be occurring. Please delete that reg value after confirming whether or not the issue still occurs with it set.
Thanks!