Im having issues entering Utgarde pinnacle and ToC 5 man.
Running straight into the portal triggers no teleport, however if I strafe into the portal it triggers with 100% success.
I cant find anything relating to this problem. And i have no idea where to look for a cause.
Any help to point me in the right direction will be much appreciated
This is how my Utgarde pinnacle portal looks in the SQL.
(heroic portal highlighted)
Updating Azerothcore repository on the server, recompiling and then importing updates fixed the issue.
Related
I am trying to build and compile an ASP.Net solution. The solution is new. Here is how I create it:
For this demonstration I avoid creating anything post-creating the project,
And here are the errors that I am getting:
All errors above, lead to the following place:
Any direction would be greatly appreciated!
Thanks!
Ok, assuming you looking to create a asp.net webforms app?
Your screen caps look ok, and it not clear why your resulting application has errors, or build issues.
I would try to create another project, different name. See if that works.
Better, try tapping windows key, type in 2022, and then right click and try run as administrator, and see if that helps. (the default source folder might for some reason require elevated rights to work).
And if above does not work?
then I would try a repair, or even re-install of VS. Perhaps the templates are messed up.
Following your exact steps, my vs2022 created asp.net web applcation without issues.
best guess:
Your VS install is messed up, re-install, or repair.
tools->get tools and features.
Then: close the modifying window, and you should see this:
Try a repair.
Thanks Albert and everyone attempting to help!
What I did that solved the issue is to click the errors, and I was redirected to the following document:
Here, I deleted every tag that was highlighted in any of the errors, more specifically, things related to Video Builder Cloud Services (VBCS), and off I go :)
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'm trying to add Application Insights to my Ghost blog running in Azure.
I have read the generic documentation about adding App Insights to a Node.js application, so I know how to do that.
What I have zero idea about is where exactly should I do that for Ghost? I've seen a lot of examples and tutorials out there, but they are all for older versions and I can't use any for the version that I have set up (1.21.3).
No matter where I tried to initialize App Insights, I either got some kind of error or just no data appeared in App Insights.
Can someone point me into the right direction? First step would be to know for sure where to put initialization code. Once I'm sure that the code is at the right place, I might have better chances tracking down the specific error.
Turns out I was overthinking this.
The solution is to put the initialization code right at the top of the root index.js.
var appInsights = require('applicationinsights');
appInsights.setup('your_ikey').start();
Im trying to figure out how DVCS Connector plugin works. Im trying to link my commits to Jira issues.
As far as I can tell it seems like my setup is correct. At least it doesnt complain about anything.
I add my issue to the comment like "MBL-10 Fixed some minor issues with.." but they are not linked with the issue.
When I try to push the "Force Sync" button it say "Last commit 7 hours ago" and it's beein saying that the entire day.
Anyone bumped into similar problems before?
Btw, Im using Jira OnDemand.
Allope,
I've recently bough Flex Builder 3 and I am completely dissatisfied with its reluctance to debug. It manages to debug a few times, but after that, it just doesn't want to "connect to the debugger".
Help?
There is no easy fix for this. You now have to join the rest of us waiting for Adobe to update Flex Builder with a fix they say they have.
You can find the long sad story here: http://bugs.adobe.com/jira/browse/FB-16153:
Basically, this is an issue that has been around for months. Adobe says it has a fix - however - they've not released that fix yet. Adobe reports it's a threading issue...
For the rest of us (waiting for this) - if you need to move forward you can:
A) Live with the problem (painful)
1) Note that in the bug text there are several attempts to work around this - sometimes people find ways to soften the issue - but no one reports a full fix
2) Note that people trying the LocalHost fix - sometimes report a gain in productivity - but in most cases they do not.
B) Switch SDKs from 3.2 (or 3.3) to 3.1 ---- No one knows why - but it fixes the problem (you can then include the SWFs you need for 3.2 directly
C) Develop on Mac [Not a smart ass answer - honestly - for whatever reason this bug is not on Flex Builder for the Mac]
Join the bug discussion - on Adobe's site - it's still active as people are still waiting for the fix.
Make sure you have the required Flash Debug Player.
http://www.adobe.com/support/flashplayer/downloads.html
If that doesn't help, you might have to re-install Flex Builder.
Are you running it on windows vista? It may be this issue:
http://blogs.msdn.com/expression/archive/2009/03/16/page-cannot-be-found-issue-when-previewing-via-expression-blend.aspx
The page is about silverlight, but I ran into the same issue a while back with the flex debugger, and had to add the following to my host file (which windows defender removed):
127.0.0.1 localhost
This is expanded more upon here:
http://circstar.com/FlashLabUnderground/?p=64
I've had similar problems but every-time it refuses to connect to the debugger i have justed downloaded and reinstalled the flash debugger and it works fine. It's a pain but until adobe do anything what can we do?
Have you the tried FlashDeveloper ide? you can build flex project with it and it quite frankly alot better than flex builder for code writing (not ui work).
Hope this helps
Jon
I'm not sure if you have the same symptoms, but I came across a similar problem on one of our development machines after installing Flex Builder 3. When trying to run our app in debug mode, flex builder took a long time to launch the app and eventually timed out, displaying some message about not being able to connect to the debugger.
I found this solution which worked a treat. While Flex Builder is trying to launch the app:
Go to the browser page containing your app/swf, right-click on the swf to bring up the flash context menu.
Select Debugger
Select Other Machine
Enter 127.0.0.1 in the text field
Click Connect and hopefully it works.
NB: If Flex Builder tried to launch the app in Firefox, the page never appeared. It was only when it launched in Safari that I was able to access the browser page and the flash context menu.