Lol. Monero's developers aren't capable of developing the coin, but they pretend they are.
Lol. Bytecoin's developers aren't capable of giving us a proof about Monero being a scam, but they promote it is. |
|
|
|
Last post from the dev was 2 weeks ago. Inactive much?? Why does this happen when coins like Bluecoin or Darkcoin can be consistent in their approach for community talk? not let days or weeks go by without talking to people. That's just absurd. Maybe I think outside of the box too much. Monero Missives
August 16th, 2014
Hello, and welcome to our eleventh Monero Missive!
Major Updates
- updated by fluffypony
Wow, climb outside of your box, much? I agree. The above list should take no longer than 10 minutes, not 10 days. Despite spam attacks and heroic emergency weekend fixes.  Most of the missives are written days before their release. Fluffypony always has to wait for third-parties to implement stuff which are going to be mentioned in the upcoming news, thus, delays may occur. |
|
|
|
...
..
Thank you for the reports, you cannot even imagine how useful they are for me!  The next version will have a fix for your problem: It appears that there is no 'AccountData' directory in the GUI's location, thus, imported files cannot be copied over there. A temporary solution is to create the 'AccountData' directory yourself before importing an account. |
|
|
|
The Monero XMR Scam Uncovered1.2. How much is the fish? A weird factCome-from-Above has donated 5000 XMR for the XMR GUI wallet. Based on XMR and BTC prices on July 19, 5000 XMR = 5000 * 0.00455 = 22.75 BTC 5000 XMR = 22.75 * 627 = $14,624 Can you even imagine somebody wanting the GUI wallet so badly that he donates $14,000? For an already available totally free software? Which runs on .NET and cannot be used without an ugly extension? While the market price of such a development would be way beyond $1,000, more like 1 BTC? I'm not even sure which of the two explanations is worse. Try answering yourself: Case 1: a whale donating $14k to a XMR wallet developer and buying hero accounts Case 2: a shill account pretending to have donated $14k and buying hero accounts As a side note, the GUI wallet developer Jojatekok has quite an interesting activity history. He's commenting only on XMR thread and is mainly supporting his wallet only. Doesn't he look more like a maintainer of GUI thread to help conceal that all GUI wallets are being developed by the core team with no 3rd party developers around the coin? I do not want to seem too obsessed with the conspiracy theories, but those things just don't add up. I just came here to gladly declare that my BitcoinTalk account was primarily registered in order to participate in a bounty for an open-source GUI wallet. If you are curious, one of my internet friends started teaching me how to program 3 or 4 years ago in VB.NET (I also have to admit that I had little experience with GML before). Last year, we switched to C# for its greater adoption rate and better performance. Now, I am 16 years old, and wanted to try out myself in developing software for a competition, and it turned out pretty well. I received a little more than 530 XMR for the effort, but still love to maintain the project (as much as Thomas Edison adored his own "baby", the phonograph). Also, there are currently 18 translations available for Monero Client .NET, so I would be doubtful about the lack of global interest. I'm a third-party developer who cares about the users and success of Monero. As Fluffypony has already told you, I didn't know back then that Come-from-Above was a scammer, but if he is ever willing to send me 5000 XMR (even by mistake), I would donate all of it to the core development team. |
|
|
|
I tried 0.39.0 b3 the same day you upload it but it wont start my wallet, just stop responding.
How much small amounts? 1, 5, 10, 20?
Do you have a 'CrashLogs.txt' file in the application's directory? If so, please send it to me. Small amounts are based on what you think "small". Just test it first whether sending a single coin with a TX fee of 0.1 XMR works.
The initial crash happens when trying to point the wallet path setting in 39.3 to a wallet created in 38.1. When going back to 38.1, even after deleting the .config file, more crashing occurs. This may not be mutually exclusive, as the initial crash may have corrupted the poolstate.bin, causing the subsequent crashing and broken nature after reverting back to 38.1. Anyway, at this point, the latter crash doesn't really matter so much since I've fixed it. I don't have a log at this point. What really matters is fixing 39.3 such that you CAN point it to a past wallet and it can handle that properly. Maybe there's some steps to importing a wallet into 39.3 that I've missed?
I tried reproducing your problem by using an old-formatted wallet file, but didn't encounter any kind of inconvenience. How did you "import" your old wallet files? Did you use the built-in backup manager or pointed to a directory using the options? |
|
|
|
Yes, I have remove my patch just after moneropool make update . ( more 6H now ) Sorry my pool is best for network . I have not include TX with fee lower off 0.1XMR 2H after commit . I have not wait 12H and 6H after get information off patch . If i used my patch is only for my pool continue work for patience other big pool make update mandatory . My patch as only not disconnect bad pool is not impact off network . Juste old bad bitmonord continue connected to my pool . If you are not ok with my check all block found per my pool after commit mandatory update and all block 2 other major pool . I'll have to break my pool because I was the first to make update ? While others pool wait update is majoritary on network for make update ? Which is more harmful? Pool make update immediatly after mandatory update ? (This even though there a small patch) Or pool wait network make update before make update ? Incompetent developers who don't even understand the importance of avoiding DoS attacks now and in the future should definitely not be relied on. Also, please hire a translator/communicator who speaks English fluently, or else, don't host a pool. It's sad to see that you cannot even follow the steps which I provided on the previous page... I would suggest boycotting this pool for now, as the admin seems not to care about the network's security. |
|
|
|
Yes i agree is verry bad patch. Without my patch my pool is broken.
You make error. I not relay bad transaction and other node not greylisting my pool ( I not relay bad transaction )
I wait all other pool make update for remove patch .
My pool not break consensus off TX Fee.
None of the other pools are using your patch, nor are any of them reporting being "broken". Your patch breaks the consensus network because it does not prevent malicious nodes from constantly pushing bad transactions by cutting them off. An attacker can spin up 50 ec2 instances and broadcast nonsense transactions (20kb transactions filled with random data) at you at a rate of tens of thousands a second. Because you're not disconnecting their connections, you will burn CPU time verifying the transactions. Even though you aren't relaying the malicious transactions, you are creating a trivial attack vector for someone to take your pool and any nodes that use this patch out of commission. This patch is bad for you, bad for the network, and fixes an imaginary problem that does not exist. I'm not a pool operator, but if I know right, you should just: - Shut down the daemon and wallet applications
- Remove '%AppData%\bitmonero\poolstate.bin' in order to clear your TX mempool
- Compile Monero's code from GitHub
- Replace the old 'bitmonerod.exe' and 'simplewallet.exe' with the produced ones
- Set your minimum TX fees to 0.1 XMR in your node-cryptonote-pool configuration file, by replacing
"transferFee": 5000000000
with
"transferFee": 100000000000 - Start the daemon and wallet applications again
|
|
|
|
I still have the same problem as DrG. I got 0.38.1 to work again but i cant send coins, wallet stops responding, same as 0.39 alpha.
Please test v0.39.0-beta.3 with small amounts, and provide feedback about the results. It should have fixed the crash which seems to occur regularly. I tested the send function of it, and it did work, even with a payment ID. Also, ensure that you raise your TX fees temporarily to 0.1 XMR, taking action against yesterday's DoS attack! |
|
|
|
I was running the old 38.1 and tried to upgrade to 39.3 beta and that didn't go too well. I tried copying over the walletdata dir directly and it didn't like that. Tried importing it and it crashed.
So I tried to revert to 38.1. I tried to run 38.1 and it crashes. I deleted the config file under Local/jojatekok and it is still crashing under Win 7 x64. I tried reextracting it and using the same walletdata dir that I was using before trying 39.3 and no go. Here's the output:
Problem Event Name: CLR20r3
Problem Signature 01: moneroclient.net.exe
Problem Signature 02: 0.38.1.0
Problem Signature 03: 53cf8e4a
Problem Signature 04: System
Problem Signature 05: 4.0.30319.18408
Problem Signature 06: 52311185
Problem Signature 07: 2fcf
Problem Signature 08: 76
Problem Signature 09: System.Net.WebException
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 1033
Additional Information 1: 6419
Additional Information 2: 641971a8558e9c66df0cda2680aa9c10
Additional Information 3: d269
Additional Information 4: d2695b2c77403c37c2fcba3124df1d83
Same here regarding it crashing after trying to have 39.3 read a wallet.bin from 38.1. I get the following crash log: Access is denied
at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
at Jojatekok.MoneroAPI.ProcessManagers.BaseRpcProcessManager.StartProcess(String[] arguments)
at Jojatekok.MoneroAPI.ProcessManagers.AccountManager.StartInternal()
at Jojatekok.MoneroGUI.Windows.MainWindow.StartAccountManager()
at Jojatekok.MoneroGUI.Windows.MainWindow.<>c__DisplayClass1.<.ctor>b__0(Object param0, EventArgs param1)
at System.Windows.Window.CreateSourceWindow(Boolean duringShow)
at System.Windows.Window.ShowHelper(Object booleanBox)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run()
at Jojatekok.MoneroGUI.App.Main()
If you have already deleted the config file, then it's fine. As I already told some posts above, these 2 issues are shouting for an urge about comfort, so it will be easier to downgrade in the future. The issue you are just referring to is caused by badly-placed software resource files. when downgrading, please make sure that you replace the contents of the '\Resources\' folder, as it really does matter in the case of migration to rpcwallet instead of using simplewallet (or backwards).
poolstate.bin became corrupted somehow in the above crash, so bitmonerod.exe wasn't able to load the blockchain into memory, and Monero Client .NET would just sit there initializing (or crash).
So, I deleted poolstate.bin, then manually ran bitmonerod.exe, and it was able to regenerate poolstate.bin and sync the blockchain. After it was synced, I closed bitmonerod.exe, and started up Monero client .net. and it worked again.
Hopefully Jojatekok can figure out why the new beta is crashing when trying to load previous wallet.bin files.
Can you explain the crash further, please? Within which versions does it happen? Have you got a crash log, or does it just happen silently? |
|
|
|
and starting 38.1
The type initializer for 'Jojatekok.MoneroGUI.SettingsManager' threw an exception.
at Jojatekok.MoneroGUI.SettingsManager.get_Appearance()
at Jojatekok.MoneroGUI.App..ctor()
at Jojatekok.MoneroGUI.App.Main()
thats it a direct crash
In that case, delete your configuration file which can be found at '%LocalAppData%\Jojatekok\MoneroClient.Net'. As for the first error you posted, please delete your 'Resources' folder, and re-extract it from the originally downloaded zip file. These two errors are so common that there will definitely be some convenience features to eliminate them. |
|
|
|
Finally, the time has come to announce the first - considerably - reliable release which utilizes rpcwallet and the new daemon: Monero Client .NET v0.39.0-beta.3 is here!Please be aware that this is a test release. You can download it from here.DisclaimerThis release is experimental and should not be used in production, but for testing purposes only. It is meant to bring the core development team a bigger tester base for using the new daemon and rpcwallet.There is a known bug in this version which is already being worked on by the core development team: You cannot create a new wallet, but use an already existing oneHave fun using the new build, and please give feedback about it, as it would be valuable for the entire Monero team.
Any version after 0.36 seems to not be working for me. The address never initializes and when I look at the log it says invalid password but the pasword box never comes up. Is this a known issue?
It looks like it I have the same issue Hopefully it will be fixed soon I hope that this new beta resolves your issues, but you may keep using older, stable releases instead of relying on test versions.  |
|
|
|
|
The newest test version is ready to be released from my part, but I've just encountered a serious issue during the usage of payment IDs.
I have already contacted the core development team about the issue, but they told me that it's probably the cause of using an outdated branch to build from. All the compiled GUI test versions have been removed from GitHub as a precautious step towards the protection of everyone's funds (even though I called out earlier that alpha/beta versions should not be used in real world scenarios). We are working hard to resolve all these problems, and the best way should be opening up an official core test branch in order not to let this happen ever again.
|
|
|
|
run from src code in VS... http://prntscr.com/4ebr09fails on rpc start process.. (A first chance exception of type 'System.ComponentModel.Win32Exception' occurred in System.dll Additional information: The system cannot find the file specified) Process.OutputDataReceived += Process_OutputDataReceived; Process.Exited += Process_Exited; HERE --> Process.Start(); StaticObjects.JobManager.AddProcess(Process); Process.BeginOutputReadLine(); // Constantly check for the RPC port's activeness 0.39.beta 2... Access is denied at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo) at Jojatekok.MoneroAPI.ProcessManagers.BaseRpcProcessManager.StartProcess(String[] arguments) at Jojatekok.MoneroAPI.ProcessManagers.AccountManager.StartInternal() at Jojatekok.MoneroGUI.Windows.MainWindow.StartAccountManager() at Jojatekok.MoneroGUI.Windows.MainWindow.<>c__DisplayClass1.<.ctor>b__0(Object param0, EventArgs param1) at System.Windows.Window.CreateSourceWindow(Boolean duringShow) at System.Windows.Window.ShowHelper(Object booleanBox) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx) at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs) at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam) at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg) at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame) at System.Windows.Application.RunInternal(Window window) at System.Windows.Application.Run() at Jojatekok.MoneroGUI.App.Main() and 0.38.1 The type initializer for 'Jojatekok.MoneroGUI.SettingsManager' threw an exception. at Jojatekok.MoneroGUI.SettingsManager.get_Appearance() at Jojatekok.MoneroGUI.App..ctor() at Jojatekok.MoneroGUI.App.Main() You should make sure that you copy bitmonerod.exe and rpcwallet.exe to /bin/Debug/Resources/Software (obtain them from core developers' repositories). Also, the alpha/beta releases are currently NOT in a working state. I'm kinda busy right now, but the next beta version will be tested and capable to be used by a bigger (but still not the biggest) audience. Some core issues should also be fixed by the core developers before stepping back to the state of stability. Keep using v0.38.1 until further notice! |
|
|
|
Yesterday I watched the Fireside Chat, patiently waiting user-friendly GUI. Account term is more reasonable. You know Andreas Antonopoulos also don't like wallet term because it's confusing, he sees Bitcoin Core is like key-chain with all the private keys on it. I support "account", non-crypto environment can understand it better.
he really does says that, and makes sense because its not a wallet, you only hold the keys and the coins are in the blockchain... its seems xmr is giving another small but remarkable step in the right direction. question: will the new wallet give an option to recover/import old wallets (before the wallet seed being implemented) thank you monero team, amazing job! How you can recover wallet without seed? It's impossible. Only if you have *.keys file. You may use the 'query_keys' JSON RPC command with the 'key_type' parameter of 'mnemonic' (I'm not sure whether it's included on the stable branch yet). |
|
|
|
If not altered, the txt file should contain your XMR address. By the way, I have just found the issue which made the wallets unable to initialize. The wallet's RPC port was always read as '0' because of a parameter's bad capitalization. https://github.com/Jojatekok/monero-client-net/blob/master/MoneroApi/Settings/RpcSettings.cs#L16EDIT: I have also spotted some bugs in the beta core components, and have already reported them. EDIT #2: Sending coins without a payment ID will not cause the software to crash from now. |
|
|
|
I am most likely doing something wrong here, but I am using the v0.39.0-beta.2 client. I installed an older client first to create an account. Then, I installed the aforementioned beta version. I did an import of my backup, it showed my address, is caught up with a bunch of connections, but it was NOT receiving any XMR. I have been mining for a couple days and the pool shows several XMR.
So, I went to a different PC, ran the client, let it catch up, imported wallet, and now for an address it just says "Initializing". Am I missing some thing here? Any assistance would be greatly appreciated!
Same for me. I used .38.1 to create wallet and it worked. I used .39 and it worked but i coulnt send my coins, wallet just stoped responding. Then i used the last one and it just keep initializing forever.
And every newer version of wallet i got the older ones just died, they cant start.
Any solution to all this? I would be nice to pull my coins out.
You all do nothing wrong. I just got home, wanted to check my wallet, and saw that it never initializes. Something fails to operate, please be patient until I examine the situation. As for downgrading from v0.39 to v0.38.1, please remove your configuration file 'user.config' located at '%LocalAppData%\Jojatekok\MoneroClient.Net', and then, the older versions should start up fine. Your settings and contacts will be lost, though (this doesn't mean that they will have to be lost i the future, just be sure to export them into a CSV file with the built-in function ). |
|
|
|
Okay guys, XMR seems to be on drugs these days or umm well, posts. We don't want to create MoneRoad, right?!  |
|
|
|
Any news about the wallet issues?
Maybe provide a wallet and see if it works for me with new alphas/betas?
There have been a lot of improvements under the hood which are waiting to be tested (I cannot do it massively here, as my main account is on my home PC). The code has been cleaned up, and several bugs were fixed. Also, I have added a built-in option to check for experimental build updates in the first beta version of v0.39.0. All the things should depend on the core developers releasing the new monerod and rpcaccount officially now. EDIT: Version 0.39.0-beta.2 has been released, and should be broadcasted by the built-in auto-update for those who were using the first beta release and enabled checking for experimental application updates. It took a lot of hassle, but finally, the terminology has been changed from "wallet" to "account". Everyone may help again by updating the translations to reflect the changes in term usage: https://www.transifex.com/organization/jojatekok/dashboard/monero-client-netPlease keep sending bug reports and crash logs, and don't worry to request any kind of help, I'm glad to give support for anyone. |
|
|
|
I'm using v0.38.1 and received coins from pool, but I also send some coins to a exchange(Mintpal) but after 30min still no pending and can't see a transaction id in the wallet.(bitmonerod and simplewallet is open)
Also I get passphrase only if I run it in administration.
win8.1 64bit
Hi everybody, can we safely use real money within that GUI or is it some kind of "be careful, don't use real coins" type of thing?
It works for me, but crashes at times. You also have to restart it to see your received coins, as it doesn't currently refresh. This seems to be a lack of implementation of the refresh command. From monero.cc, "Getting started": If you let you wallet opened all the time, you may think that you are not receiving any monero. This is because refresh is not automatic. You must either close the wallet and reopen it of, much more elegant, use the refresh command. Actually, refresh is implemented, but the current bitmonerod.exe and simplewallet just fails silently, thus, causing the GUI not to reflect new transactions. Version 0.39.0 will solve this issue, as it uses the new daemon and rpcwallet to communicate, but it lacks the ability to create new wallets at the moment.
A lot of strange guys here, in XMR topics. Hm, i'm pretty sure that this is not coincidence.
That's because XMR devs are not so clean. If you know what i'm talking about. XMR developers are honest, but more shy than the "average" or cryptoland. That's because they don't want the news to be first instead of the actual implementation.
Hi everybody, can we safely use real money within that GUI or is it some kind of "be careful, don't use real coins" type of thing?
I use it on my own, and have sent and received dozens of XMR without any kind of failure. It can only fail where simplewallet/rpcwallet would fail too, as the application is a silent wrapper of them. |
|
|
|
The first alpha version of the 0.39.0 releases introduce a new version of the settings file, which is located at '%LocalAppData%\Jojatekok\MoneroClient.Net\user.config'. Please delete it, or if you want to keep your settings while downgrading, just open it in a text editor, and change <tt><metaData settingsVersion="4" /></tt> into <tt><metaData settingsVersion="3" /></tt>. Also, don't forget to relocate <tt>softwareWallet="Resources\Software\rpcwallet.exe"</tt> into <tt>softwareWallet="Resources\Software\simplewallet.exe"</tt>. As for your rpcwallet issue, I will look into it deeper as soon as I have access to my personal wallet at home, so I will be able to test things more toughly. It is weird that the password request box doesn't show up - some people said that it happens since v0.36.0. Do you have any problems with v0.38.1? If so, does v0.35.0 or even v0.36.0 work for you? Thanks, this works. Maybe there should also be a path option for this available in the GUI? Just tried 35 & 36, like 38.1, they seem to work fine. Only with 39 builds, password request doesn't show up. The path for storing the settings should not be altered, as the current solution is what most of your PC programs use. hi Jojatekok, (edit: its me the shoutout guy ^) i got the client up and running (3.81) and sync'd with a new wallet. then i quit. now, when i run the client, it does start syncing after a minute or two, but the wallet does not load. stays in "initializing" i have no other processes or applications running that are using the wallet.bin (that i know of)... any ideas? edit 2: i have shutdown/restarted... no effect. the crash log shows shows: Unable to connect to the remote server
at System.Net.HttpWebRequest.GetResponse()
at Jojatekok.MoneroAPI.Helper.GetResponseString(HttpWebRequest request)
at Jojatekok.MoneroAPI.RpcManagers.RpcWebClient.HttpGetData[T](RpcPortType portType, String command)
at Jojatekok.MoneroAPI.ProcessManagers.DaemonManager.HttpGetData[T](String command)
at Jojatekok.MoneroAPI.ProcessManagers.DaemonManager.QueryNetworkInformation()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
The process cannot access the file 'WalletData\wallet.bin.keys' because it is being used by another process.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.File.InternalCopy(String sourceFileName, String destFileName, Boolean overwrite, Boolean checkHost)
at Jojatekok.MoneroGUI.Windows.BackupManagerWindow.RestoreWalletFromDirectory(String directoryToRestore)
at System.Threading.Tasks.Task`1.InnerInvoke()
at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
at Jojatekok.MoneroGUI.Windows.BackupManagerWindow.<TryRestoreWalletFromDirectoryAsync>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Jojatekok.MoneroGUI.Windows.BackupManagerWindow.<ButtonRestoreBackupFromDirectory_Click>d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.AsyncMethodBuilderCore.<ThrowAsync>b__4(Object state)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Window.ShowHelper(Object booleanBox)
at System.Windows.Window.ShowDialog()
at Jojatekok.MoneroGUI.Windows.MainWindow.DisplayDialog(Window window)
at System.Windows.Input.CommandBinding.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.Input.CommandManager.ExecuteCommandBinding(Object sender, ExecutedRoutedEventArgs e, CommandBinding commandBinding)
at System.Windows.Input.CommandManager.FindCommandBinding(CommandBindingCollection commandBindings, Object sender, RoutedEventArgs e, ICommand command, Boolean execute)
at System.Windows.Input.CommandManager.FindCommandBinding(Object sender, RoutedEventArgs e, ICommand command, Boolean execute)
at System.Windows.Input.CommandManager.OnExecuted(Object sender, ExecutedRoutedEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)
at System.Windows.Input.CommandManager.TransferEvent(IInputElement newSource, ExecutedRoutedEventArgs e)
at System.Windows.RoutedEventArgs.InvokeHandler(Delegate handler, Object target)
at System.Windows.EventRoute.InvokeHandlersImpl(Object source, RoutedEventArgs args, Boolean reRaised)
at System.Windows.UIElement.RaiseEventImpl(DependencyObject sender, RoutedEventArgs args)
at System.Windows.Input.RoutedCommand.ExecuteImpl(Object parameter, IInputElement target, Boolean userInitiated)
at System.Windows.Controls.MenuItem.InvokeClickAfterRender(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run()
at Jojatekok.MoneroGUI.App.Main()
Unable to connect to the remote server
at System.Net.HttpWebRequest.GetResponse()
at Jojatekok.MoneroAPI.Helper.GetResponseString(HttpWebRequest request)
at Jojatekok.MoneroAPI.RpcManagers.RpcWebClient.HttpGetData[T](RpcPortType portType, String command)
at Jojatekok.MoneroAPI.ProcessManagers.DaemonManager.HttpGetData[T](String command)
at Jojatekok.MoneroAPI.ProcessManagers.DaemonManager.QueryNetworkInformation()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
I'll be sure to check your case as soon as I get home. It seems that your daemon RPC cannot be used, it's probably because it conflicts with an application which already uses its port (which is - by default - 18081). In the file explorer, go to '%LocalAppData%\Jojatekok\MoneroClient.Net', and open 'user.config' with a text editor. You will see a line like this: <network rpcUrlHost="localhost" rpcUrlPortDaemon="18081" rpcUrlPortWallet="18082" isProxyEnabled="false" proxyHost="" /> Try adjusting your daemon and wallet ports between 0 and 65535, until the software works. hey, so i changed the port numbers but no effect. however, when i run the bitmonerod , it shows the port numbers are not being updated... so while the user.config file is changed, its not being updated when running everything again... Please try deleting your application settings file, as described above. i deleted the user.config file. it created a new file on next startup. this looks different than the previous version. there are no port numbers listed in the file anymore. using the cmd line: C:\> netstat -a -b it appears that the lsass.exe (Local Security Authentication Server) is using TCP port 18081 ... edit: ran this line: netsh int ipv4 set dynamicport tcp start=10000 num=1000 to force the random port assignments to be >20000. the wallet.bin still can't be loaded and stays in initializing. running the bitmonerod .... i see 2014-Aug-09 10:27:23.412709 Module folder: C:\Program Files\monero-client-net-v0
.38.1-x64\Resources\Software\bitmonerod.exe
2014-Aug-09 10:27:23.416698 Initializing p2p server...
2014-Aug-09 10:27:23.427642 Binding on 0.0.0.0:18080
2014-Aug-09 10:27:23.430726 Net service binded on 0.0.0.0:18080
2014-Aug-09 10:27:23.431988 Attempting to add IGD port mapping.
2014-Aug-09 10:27:27.444946 No IGD was found.
2014-Aug-09 10:27:27.444946 P2p server initialized OK
2014-Aug-09 10:27:27.446994 Initializing cryptonote protocol...
2014-Aug-09 10:27:27.449202 Cryptonote protocol initialized OK
2014-Aug-09 10:27:27.451000 Initializing core rpc server...
2014-Aug-09 10:27:27.452318 Binding on 127.0.0.1:18081
2014-Aug-09 10:27:27.453024 Core rpc server initialized OK on port: 18081
2014-Aug-09 10:27:27.456393 Initializing core...
2014-Aug-09 10:27:27.461014 Loading blockchain...
2014-Aug-09 10:28:06.233748 Blockchain initialized. last block: 165952, d0.h0.m1
1.s55 time ago, current difficulty: 1308186462
2014-Aug-09 10:28:06.252720 Core initialized OK
2014-Aug-09 10:28:06.256679 Starting core rpc server...
2014-Aug-09 10:28:06.261819 Run net_service loop( 2 threads)...
2014-Aug-09 10:28:06.276680 [SRV_MAIN]Core rpc server started ok
2014-Aug-09 10:28:06.280876 [SRV_MAIN]Starting p2p net loop...
2014-Aug-09 10:28:06.289837 [SRV_MAIN]Run net_service loop( 10 threads)...
2014-Aug-09 10:28:07.290775 [P2P7]
Your daemon works just fine now, it still seems to be a port conflict for me. Adjusting the daemon and wallet ports should probably help you out. |
|
|
|
|
Show Posts
