I have a DotNetNuke Module created in DNN 4.9.2. It runs fine on my dev machine but when I post it to the live server, I just get a blank screen, well my skin with no content.
I have installed and then uninstalled, then reinstalled the module, same issue.
I must be overlooking something. Can anyone outline some ideas on how to trouble shoot this issue. I have done the following:
Check code - exact match
Check DNN Event Log - clean
Look for errors - none
Restart Site - same issue
Check Windows Logs - clean
Bang Head against desk - same issue, although now I have a headache
Any other ideas would be great
Make sure that the "Mode" selection at the top of the control panel isn't on Layout.
Are you running as an administrator? Otherwise, do you know that the user has rights to see the module?
The answer was a bug in my code. The reason I didn't see an error was because that an xslt file path was wrong and it didn't kick in my try catch. I corrected the path and violà.
Related
Below you can see the output I get when I try to run npx react-native run-android. It suggests some options to try in order to further pinpoint the problem, however they don't work with the aforementioned command so I assume that they are related to a gradle (just an educated guess).
I know ZERO about gradle; I have just seen the name here and there and in the output shown below. So please keep that in mind when you answer. If I need to learn how to run some gradle command(s) directly, please be as verbose as possible in your answer.
The project was working fine just a bit ago, but I wanted the ability to force portrait mode for certain screens but without configuring my entire app to always have to stick to portrait mode. So I found what looked to be a solution in the react-native-orientation-locker module. I installed it with yarn and then proceeded to update files as directed: https://www.npmjs.com/package/react-native-orientation-locker.
After updating the appropriate files, I got an error that suggested axios was the problem. I uninstalled and reinstalled axios. After that didn't work, I proceeded to undo all the file changes I had just made. Then I uninstalled the react-native-orientation-locker module.
To my knowledge, I have undone everything I did between the time the project worked and stopped working.
Sadly, I had not put this into source control yet (a mistake I won't make again), so I can't revert.
Where to go from here?
Problems like this are hard to pin point. What you can do is open the android project in android studio and see the logs as the project is being assembled. I assume you do not have much knowledge about android either so you might need some senior resource to help you.
What I usually do in this case is open android studio and if I am lucky enough, it tells me which file has an issue and I go to the file and do what android studio suggests me. Some times it fixes the problem and sometimes it doesn't.
Another thing I would like to mention is that the documentation of the package you are using is important to follow. I assume you did that already but I would suggest to review it narrowly and closely.
Another guess I can tell you is try to go to your-project/android/build.gradle and over there, you'll see something like this in the start. The package you are using mentions something about target SDK 27. I think you should check that out too. May be it helps
Lastly I would say always use source control while working with react native. It can easily blow up at any time so you should always have a safety net to fallback to :)
I have a radio button that is represented as a pbdatawindow, when I run setcelldata to pick an option it works fine on my laptop but fails on my colleagues laptop. If we try the run the command again on my colleagues laptop we get a fatal error from UFT.
The only difference between my UFT install and my colleagues is that my colleagues version is installed in French. Has anyone seen a similar issue?
PbWindow().PbDataWindow().SetCellData 1,1,""
Few things to try:
What version of uft are you using? - perhaps check for newer of see if there is a patch available?
Jump onto the microfocus knowledge base and see if there is anything around power builder.
You say the machines are the same but does that include every application too? In the past I've known that if you install applications after uft it can break its references. Try uninstalling and reinstalling uft. There is a repair option but uninstall/reinstall is normally more thorough.
Try and clear out all your temp and user settings.
In your user profile backup then remove all folders with mercury, hp, Hewlett-Packard and microfocus.
-The go to %temp% and clear evetything.
Try and pin down the problem - Has your colleague tried the English version or uft? - if that works, is it an option? (everyone use the same version)
If it doesn't work it suggests it's your colleague's machine as opposed to uft.
Is evetything such as the resolution and browser/application versions the same? Or simply try another French localised machine?
What's the fatal error? Does it provide any clues on why it failed?
Finally, You're paying a lot for commercial software. Don't suffer in silence :-)
Log a support call with microfocus. It's a bit long winded but Back in the day they used to be pretty good at helping. They'll ask you for logs and knowing how to get that is good to know.
There's more to try - let me know how you get on.
I have a custom bootstrapper (C# WPF) and it works well enough. If the installer gets run from the command line after it was installed, it brings up a window allowing the user to select if they want to modify, repair or uninstall. So far so good. Modify mode starts the UI which ends up calling Bootstrapper.Plan(LaunchAction.Modify). The problem is that if I call it from the launcher UI it immediately complains that a prior install requires a reboot.
I have not found any good examples on what this should do. Even the WiX mailing list came up blank.
Any ideas?
It would be helpful with the screenshot for that reboot message - just to get a feel for where it might be coming from and to get a literal string to search for. Did you have a look in the WiX source code yourself btw? (WiX 3.111 branch)
I started writing a lot of stuff about reboots. Not good. Maybe just some questions instead:
Does this happen every time you invoke modify and is it reproducible on more than one computer? Or maybe it is just Windows Update acting up on a problem computer?
I assume you have rebooted the computer where you see the problem and you see the problem again when you re-launch the bundle?
Do you schedule any reboots inside your MSI files during the initial installation?
Either using the ScheduleReboot action or a custom action which schedules a reboot with a call to MsiSetMode (for example)?
There is a long explanation here why such reboot-constructs cause problems, but that may be besides the point. Essentially badly configured reboot-constructs can trigger spontaneous, unexpected reboots without warning when packages are run in silent mode (plus other problems).
Could you try to run the test VBScript found in this answer: WiX behaving badly on XP machine with windows update issues in order to check if the script reports a reboot being necessary?
Other than that I guess you could try to run Burn yourself in debug mode (not sure how much plumbing that would be to get running) or perhaps first try a ProcMon.exe session to see if you can see something obvious. The latter should be quick to do?
There are some registry locations you can hunt down to see if you can figure out what triggered the reboot warning. Get-PendingReboot-Query. And a similar PowerShell script.
So in the end it was user error. :-( O well. I did learn a lot about how to figure out how Windows checks for the need to reboot etc.
The issue was simple in the end. During the modify run it was uninstalling, then reinstalling a number of services. The problem is that when it runs (seeing as you have to set it to repair to get it to work) it copies all the files again and the services were still running at the start of the install. The fix was to uninstall anything that might lock a file before the actual file copy starts and that solved the issue for me.
Thanks for your help guys, all the info helped me look in different directions until I found the issue. Awesome community as always!
Okay, This question has probably been asked before but I can't seem to solve it with anything that I've seen.
I published my program and tried setting it up on another computer. At first it gave me this error:
"Unable to install or run the application. the application requires that assembly microsoft.reportviewer.processingobjectmodel version 9.0.0.0 be installed in the global assembly cache (GAC) first."
After searching I found that including everything in the 'Application Files' before publishing made that go away, only to be replaced with
'Application cannot be started. Contact the application vendor.'
After searching and doing a lot of things on the computer that I want this program to be setup on, I checked (Crystal Report Basic For Visual Studio 2008 (x84, x64)) in the Prerequisite.
On the Computer that I need this program on, it won't download this at all. It gives me a message box to either retry or cancel.
Some pages suggest that the Crystal report package that automatically downloads is not the right one. When I tried following what is said here, I got stuck because the links won't open.
Any help appreciated, It's frustrating because I've been working on this program for months and I get stuck on the last step :/
oh .. and ... I don't know if this has anything to do with this, but I built the program using Windows 7, then updated to Windows 8, then updated to Windows 10.
I finally managed to make it work :)
Here is what I did:
I followed this video and I was able to install my program to the other computer.
When I opened it, I got a problem that the program can't find my MS Access DataBase, so I went to the setup project -> Right click -> add -> File, And I navigated to my original project's folder and added everything in there, and Viola! ... It works :)
I hope this helps somebody else :)
I have a VB.NET ClickOnce application that I am trying to install on my computer. Previously, I was able to install and run these apps without issue. Now when I install the application, I can see the flash of a window opening, and then nothing. (There are also no processes left hanging or anything when viewed with the task manager.)
After some digging around I noticed that there are files in my Temporary Internet Files with names like "FusionBindError" and then my application name and different DLL names.
I have done everything I can find on the net to do, reinstall applications, reinstalled the .NET Framework, deleted my Local Settings folder and relogged in.
Does anyone out there have any other ideas for me to try?
I tried the Mage.exe suggestion, but it failed to help. Same with the other installation location suggestion. The application flashes at the bottom of the screen but does not open. I have tried using FUSLOGVW to check the bindings and nothing shows up in there. (Good or bad, there are no binding entries.)
Have you tried using mage.exe? This is a command-line tool that comes with .NET framework. Start up a VS command prompt, and try mage -cc. This will clear your applicaiton cache and will force a new click-once download. This is the first thing I do when my click-once applications fail and it works 99% of the time.
A couple of suggestions:
FusLogVW isn't working for you because you have to enable assembly binding failure logging inside the registry. This MSDN article describes how to do this.
Another thing that comes to mind is, perhaps the ClickOnce app install, or perhaps the whole ClickOnce store is corrupted. Try deleting the ClickOnce app store then reinstalling the application.
It's possible that new prerequisites were added that you don't have on hand. If the URL you are using points directly to "my.application" or whatever your equivalent is, prerequisites won't be processed.
So try pointing to the setup.exe that is created in the same directory as the .application file.
Other than that, it sounds like you're doing all the right stuff...
Also, it could be useful to run the fuslogvw utility on a machine where the application actually works. Or reflector.
And then see if indeed any of its dependencies being loaded surprise you.
Also, for these types of errors, be sure to check if disabling the antivirus resident protection helps. Sometimes it causes problems accessing assemblies' manifests and such.
I uninstalled my Kensington Mouse software, and that resolved my installation errors.
Who knew that mouse software that I never used could cause so much trouble??
Sometimes if your machine is working for days this problem will show up. Try to restart your machine. The same problem happened to me and it disappeared when I restarted my machine.