I cant flush the shared object in my project. What can I do for that problem?
Make sure that the URL is valid. I had the same problem with a double slash (//) in the URL:
http://localhost/myProject//MyProject.html?debug=true
Flash should be allowed to store data to your hard drive. You can configure storage settings here :
http://www.macromedia.com/support/documentation/en/flashplayer/help/settings_manager03.html
I was having the same problem in Windows 7. I went to control panel and allowed storage from there. you can do the same at
Control Panel -> System & Security -> Flash Player
"Error #2130 Unable to flush sharedObject" can also happen when you do flash() on remote object with debug(!) version of Flash player installed.
Uninstall debug version and install a normal one to solve the problem.
Related
I've been at this for past 2 days and I'm getting weird errors from the store.
I'm trying to upload an update to my application "CoManga" via the store and it's not working out.
I'm working on Xamarin.Forms (UWP) and before making the appxbundle, I made sure and "associated my app with CoManga" from my developer account. All the information over there matches and should work fine without any issues.
Then I made a release of my UWP app, got the bundle and I tried to upload it to UWP.
It said that the Publisher info is different, so it couldn't upload. This is weird because I tried signing the bundle with my developer account itself.
Now, I tried building and signing the app bundle from app center. I got the appxbundle and that I tried to upload. But, since today it's giving me weird error :
The package comic_dl.UWP_2.1.15.0_ARM_x86_x64.appxbundle is taking a
long time to process. If this isn’t completed soon, try refreshing the
page, or remove the package and then upload it again. If you continue
to see this issue, contact support.
This package I tried to build from my system manually : https://drive.google.com/open?id=1VVvF6IB70R2DKNUgBJcqw-HryL1LIwgo
This is what I got from App center : https://drive.google.com/open?id=1o0sGKU2AKVgrcTelIoRFz7QCe8Do0WJ3
This is the Store ID : 9N81F8B5WW93
Can someone guide me what I might be doing wrong/missing something.
Thanks
EDIT Update : So, I followed the suggestion and contacted Microsoft's Team for help on this issue. After 3 months of multiple contacts, I was able to get someone to reply back and follow the case. Even they tried things on their end and I tried by deleting all the certificate files I had in my current project and tried to manually build the manifest file and then it worked. I'm not entirely sure what worked out in the end. But, you can try these things if you run into this issue.
1.) Clean your project.
2.) Delete .vs directory.
3.) Look for any certificate files in your project. Back them up somewhere else and then delete them from the project (Don't exclude from project, just delete them entirely). Clean and rebuild your solution.
4.) Check if the application is already installed on your system (When you debug, VS will install your UWP app on your machine to run it). If it's installed, uninstall it completely.
5.) Make a backup of your manifest file and try to create a new manifest file.
These are the links I received from Microsoft Help:
PFN and package publisher name must match values here: https://partner.microsoft.com/en-us/dashboard/products/{YourAppID}/identity
Update manually: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/how-to-create-a-package-manifest-manually
Update in VS: https://learn.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/generate-package-manifest
If these values were pulled from test certificate, partner needs to update their test cert: https://learn.microsoft.com/en-us/windows/msix/package/create-certificate-package-signing
I think this problem is not caused by anything code related, but rather it is a problem on the Store side. I would suggest contacting the Store support, they should be able to investigate if there is something wrong with your app package or the problem is on their side.
For support go to the official website, click the Contact Us tab and fill out the form accordingly.
The team should be able to advise even for the first error with different publisher info. If your app was always associated with the same account, there is no reason it should give you such an error message.
I had this issue gazillion of times. It is so frustrating. That error message isn't useful at all.
Anyway - I think it is something in Package.appxmanifest, something in Identity tag.
Retrieving some necessary info from store helped me.
Click right on your project -> Publish -> Associate App with the Store. This will update Package Display Name,Package Name,Publisher ID,Publisher Display Name and Version with correct values (within Package.appxmanifes).
Also be careful with version number. The last from numbers must be zero. 1.1.1.0 is fine, while 1.1.1.1 is not.
I am trying to save a simple HTML file in GitHub's Atom text editor, but I get the following error:
Unable to save file 'C:\Users\Alexander\Desktop\Looking good website\products.html'
EBUSY: resource busy or locked, open 'C:\Users\Alexander\Desktop\Looking good website\products.html'
This seems to be a known issue when I check the atom git repo. See here.
Now somehow even though there are multiple issues opened with the same problem on the atom git repo I don't see a solution.
How do I solve this error?
I am not sure how to replicate this issue but initially the file was saving fine, but now suddenly I have this problem and I don't see any obvious solution.
screenshot :
Can somebody help please?
Re-creation of error ::
Error in Atom :
What i see in process explorer::
For some reason Atom doesn't want to save files, that you have currently open in your Windows Explorer. At least that was the issue on my workspace.
I was able to solve this issue by closing all applications using the file. I was viewing a webpage locally, so I killed the browser and windows explorer then Atom let me save the file.
Hate to necro an old thread but I just ran into this myself and believe I have found the problem; the Preview Pane in Windows Explorer.
Either deselect the file in Explorer after opening or turn off the preview pane altogether.
Get Process Explorer from LINK and use Ctrl+F to find the process keeping the file open (see MS support link)
Then tell me what you see, and I'll expand the answer :)
My anti-virus (Bitdefender) thought atom.exe was an unsafe application so it kicked on Ransomware protection.
Hope this helps somebody
I’ve been having the same issue, and I found what was causing it for me.
I had Windows Defender Ransomware Protection enabled on my computer, and I was trying to save to a protected folder. Even though I had whitelisted the atom app, and didn’t receive the usual warning from Windows, it was preventing me from writing to the location. Disabled Ransomware protection, and suddenly Atom can save there again.
Not sure if you’re in the same boat, but maybe give it a try if you have Ransomware Protection enabled. Or maybe some other anti-virus with the same feature?
I'm attempting to create a custom WordPress theme using MS WebMatrix and am encountering the following error when trying to install the WP app:
Error 2738: Could not access VBScript runtime for custom action
This occurs when the download attempts to install Web Deploy 3.5. I'm currently running Windows 7 64-bit OS.
The research that I've done indicates this is error stems from "VBScript being not properly configured to run on the PC."
The solutions I've encountered and tried - to no avail - are:
Run MS FixIT
Re-registering the VBScript dll via cmd prompt - c:\windows\syswow64\regsvr32 vbscript.dll
Run the System File Checker tool sfc /scannow
[Note: I do not have, nor have I had McAfee installed - I've seen reports that in some instances the McAfee installation can cause the wrong vbscript .dll to be registered]
Outside of doing a factory wipe - which I'd like to reserve as a last resort or completely scrap using WebMatrix entirely - I've run out of potential solutions searching this specific problem.
Has anyone had success with this issue outside of the solutions posted here already? Any help would be appreciated.
So, I discovered a solution to this issue that hasn't been covered well online, so I'm posting it here.
A steadfast solution to resolving this error if running Windows 7 64-bit OS:
Open your registry editor
Start -> Search -> Type "regedit"
In the editor, click on:
HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\Wow6432Node\CLSID{B54F3741-5B07-11cf-A4B0-00AA004A55E8}\InprocServer32
Check the value for (Default)
If it's anything other than C:\Windows\SysWOW64\vbscript.dll that's where your issue is originating
Make sure you have the correct permissions to edit the value for (default)
Right Click on InprocServer32 -> Permissions -> Give yourself "Full Control"
Now edit (Default) and set it to C:\Windows\SysWOW64\vbscript.dll
Reboot
This should fix any issues that might have been encountered during the execution of custom VBScript during Web Deploy download.
We have built a WebDav Service with your Engine and have a one problem when we create a new Folder or File:
The new folder / file is created successfully, but not showing in the Windows Explorer. Only if you press F5, the new folder / file is showing (and the name is already selected to be edited).
This behavior is reproducible even with a blank WebDav Solution.
We can reproduce this on Windows 7 and Windows 8 (8.1) using WebDav .NET Server 3.8 and the latest 3.9.
Is there a way to get around this “refresh-problem”?
I solved this issue but clicking in the folder explorer at view > options > then i restored to default and everything is back to normal.
I assume this issue is in Windows Explorer on a single computer. Most likely the WebDAV server-side code is failing with with some exception. Here are some ideas how to detect what is wrong:
Unmount network connections executing 'net use * /DELETE' in a command prompt, this will unmount WebDAV connections too and simulate 'clean' environment.
Retry reproducing the issue and examine your WebDAV logfile. By default it is located in /App_Data/WebDAV/Logs/ folder. Are there any exceptions in it?
Use Fiddler tool or any other debugging proxy to capture and examine HTTP requests. Are there any failed requests?
In case you are creating a folder/file on one computer using Windows Explorer (Microsoft Mini-redirector driver) or IT Hit Ajax File Browser and expect the files list to refresh automatically on another computer this would not work. Mini-redirector does not support any notifications from server and WebDAV does not submit any notifications, you need to refresh the files list manually to see the new items created.
I found this video on Youtube that explains in very much detail how to fix this problem: https://www.youtube.com/watch?v=UUiCPsQquqc
It is a bit lengthy, so I'll just quickly sum it up here:
The reason for these problems are one or more (broken) Shell Extensions that prevent the refresh of the Windows Explorer
To fix it, open up regedit.exe (requires admin privileges), do a search for the Registry Key "DontRefresh". If it is "1", set it to "0". There might be multiple matches for that Key, so repeat until all Keys have the value "0".
This might not work immediately, you may have to kill and restart your explorer.exe process (easiest to do with the Task Manager). Or you can simply reboot your computer. In my case, it worked immediately.
According to the video, the Keys should only be located under HKEY_CLASSES_ROOT/CLSID, but in my case I could only find such Keys in HKEY_LOCAL_MACHINE/Classes/Wow6432Node/CLSID.
I figured it makes most sense to simply search the complete Registry, it does not take very long.
I tred a lot of hacks, from scanning the system, to recreating the profile to hacking Registry keys and hives.
Finally what worked for me -
Right click on desktop
Select Personalize
Click Themes
Click Change desktop icons
Click Restore default & OK
And instantly it began to auto refresh with a new folder, rename, delete, copy, etc.
I have been trying to work on integrating a NewsLetter for a companies local intranet and I keep running into the same error that everyone seems to be getting. I am running this on IIS 5.1 and on error exists at Server.CreateObject(ADODB.Connection), also the purpose of the ASP code is to read an Excel file
Error Type:
Server object, ASP 0196 (0x80040154)
Only InProc server components should be used. If you want to use LocalServer components, you must set the AspAllowOutOfProcComponents metabase setting. Please consult the help file for important considerations.
I have tried the solution to locate to my AdminScripts directory and setting the boolean value to True with cscript adsutil.vbs set /w3svc/aspallowoutofproccomponents True and then verified by cscript adsutil.vbs enum /w3svc > verified.txt
Opening up the textfile, it does show that the value is set to true but I run into the same error again when trying to access the ASP page. I am at a loss, I figured after reading all those people post questions that I'd ask the question myself.
I cringe at the sight of that error messages, please make my nightmare end.
Its a bizare error to be getting in the first place. Why would the simple ADODB.Connection object be considered an out-of-process component?
The only thing I can think of that might cause this is if someone has accidently dragged the ADO dll into a COM+ Service. Check the set of COM+ Services anything unusual installed there?
In an attempt to repair you could download the latest MDAC from Microsoft's download area and re-install it on your machine.
Enabling out-of-proc components to is not the answer ADODB.Connection should not be out-of-proc.
Next Step
Fire up Regedit, find in Keys the key value of {00000514-0000-0010-8000-00AA006D2EA4} under
HKEY_CLASSES_ROOT
You should find an InprocServer32 key with a default value: C:\Program Files\Common Files\system\ado\msado15.dll
The ProgID should ADODB.Connection.2.8.
I had to use:
Regsvr32.exe "C:\Program Files\Common Files\system\ado\Msado15.dll"
in the command window to have the InProcServer32 key appear, thank you Anthony.
Everything is up and working now. My nightmares are over!