I have installed a fresh instance of AX 2012 R3 on my system. When I try to start the service on my machine i get the following error:
Note: When I try to start the service through Local system it works. But I want to start it through the account NT Authority/Network Service. Any suggestions?
Another anomaly is that when i try to install DIXF it gives me the following error: "Verify that you have enough privileges to start the service"
It sounds like you've narrowed the issue down yourself. Do you need to have it running as the network service account? Run it as your user or another user with access to SQL.
I'd say that it's a permissions issue to SQL and/or file permissions on the machine the AOS resides on.
https://technet.microsoft.com/en-us/library/dd362055.aspx
Debugging a crashing AOS server is not a simple task.
As I see from your Event Log you are running build number 6.3.164.0 which is the RTM build of 2012 R3. Many hotfixes have been released since and there is a good chance your problem goes away with just installing the latest kernel build. See Overview of Microsoft Dynamics AX build numbers for links to more recent builds.
Running a newer kernel with an older application build is supported, but since it's a fresh instance I'd update the application too.
If you would have a go at debugging this yourself you could try to get a memory dump to analyze with windbg. Refer to this article So your AOS crashed, is hanging, or you just want to see what it's doing .
Unfortunately my results with that approach have been mixed. Unfortunately we don't have access to all debugging symbols we need, and in this case, since it crashes immediately on startup I don't know what to expect.
Your third and last option is to open a support ticket with Microsoft and provide them with memory dumps, but their suggestion will be to update to a more recent build anyway.
Related
I have designed a SSIS project and deployed it to SQL server and also created the job to run on daily basis but its giving me this error when executing this as job (doesnt give any error within VS):
There is this CLSid in this error message but there is no application associated to it in
--> Component Services -> Computers -> My Computer -> DCOM Config
But this CLSid is registered inside registry editor
About this particular task on which this error is occurring: This is a script task which is modifying and deleting the un-wanted rows from the excel file in which I am trying to write SQL table data.
Script task code looks like this:
I have been working for hours now trying to fix this problem but no success. Kindly guide me how can I fix this issue. If any other information is required related to this project, please let me know....
Doing Excel automation in a SQL Server agent job is totally unsupported and probably won't work.
To have even a ghost of a chance of making this work you'll need to run a real desktop session on the server and automate Excel in that. Excel expects a real user to be logged in with a full profile. And Excel has failure conditions where it displays a popup window, which you'll need to be able to access via remote desktop.
You can read and write Excel files on a server with the OpenXML SDK, without actually having to run Excel. There's also a wrapper library called ClosedXML which you may find easier to use than using OpenXML directly.
tl;dr;
You need to install Office (Excel) on the server AND ensure that you install it in a manner that mirrors the SQL Agent's expected bit-edness. Default for Agent is going to be 64bit, default for Office is still 32 :(
Error guessing
You have a script task that uses the Office interop libraries to delete some rows (2 through 11?) out of a spreadsheet.
You have Office installed on your machine and therefore you have the libraries installed. Excel still has COM based "stuff" in it, thus the interop and errors shrieking about the CLSid, registry, etc but that's likely just secondary errors because there is no base "application is not installed" exception to be thrown.
If Office is installed, then ensure your agent execution model matches the version of Office. If 32 bit Excel is already installed, don't potentially break everyone else's stuff by uninstalling and reinstalling as 64 bit, just got the Advanced section of the SQL Agent Job Step and check the 32bit box.
Once all that's done, then if you're still getting errors but new ones, then the existing comments mentioning permissions may come into play - it depends on where the Excel document actually exists (on the computer where SQL agent can access vs on the computer where it cannot vs networked drive)
Good luck in not finding people on the sanctions lists.
Running SSMS 18.6 causes the program to launch, hang, and then crash. There is no error message given, the program simply terminates before any action is taken and nothing is connected.
I've uninstalled and deleted all files for SSMS, Visual Studio, and SQL Complete.
I tried the 18.6 and 18.5.1 versions of SSMS to no avail.
From https://dba.stackexchange.com/questions/237086/sql-server-management-studio-18-wont-open-only-splash-screen-pops-up/237087#237087 :
I have tried copying the Interop.8.0.dll file from privateassemblies into public. No effect. The line in the config file mentioned here is already commented out in the recent release of SSMS.
From Sql Server Management Studio closes immediately after startup :
I have tried renaming or deleting the package file listed here and removed the relevant registry key. This causes SSMS not to open at all and Windows to issue an alert sound. No other effect.
From https://social.msdn.microsoft.com/Forums/silverlight/en-US/9d0e2459-eb74-46e8-a983-05ae2ba18977/ssms-crashes-on-startup?forum=sqltools :
I tried to repair .NET framework. No effect.
I was only able to install and successfully connect on SSMS version 17.9.1
I can provide Event Viewer details if anyone is willing to help me troubleshoot. I have a .NET Runtime error and two application errors- one is event name CLR20r3 and the other is APPCRASH. Happy to provide more information if needed.
While I can't speak to the exact reason it happened, I found a solution. Whatever the issue was, I discovered it was user specific and limited to my machine. Other users were able to access SSMS as normal on my machine as was I on theirs.
I happened to remember that the AppData folder exists and is just hidden, so I used an administrator account to copy that from a working user and rewrite the files in both of mine that were not used in some background process. This allowed me to once again access SSMS both as my regular user and with my elevated administrator account.
I had this same issue (it happened all of a sudden perhaps due to a windows update). I also tried all the other solutions listed above, but the only thing that worked for me was to uninstall and then reinstall version 7.9.1 like the original poster recommended.
In my case I only have 1 user on the computer, so the other user accounts being able to access was not applicable.
I have an application which uses the OCI 7 API. This application is successfully deployed on a variety of configurations like
WS2003/Oracle9 and WS2008 R2/Oracle12 (r1). I am now trying to deploy the app on WS2012 R2 but I am facing a frustrating issue where the application crashes with an illegal access somewhere in oranls12.dll. This makes think that it has something to do with the locale and/or system variables. I have checked that the NLS_LANG system variable is set as the same the database uses which is AMERICAN_AMERICA.WE8MSWIN1252.
I have tried using the binary which I know works on WS2008, and I have also compiled it on WS2012. It still crashes. Does anyone know what is wrong, or have any pointers on how to debug this properly?
Any details needed I will provide.
To answer the comments below, the app uses the OCI 7 API, which is still provided with the newer drivers. The app itself is compiled against OCI 12. The database running on the server is Oracle 12.1.0.1.
An attempted deployment from (localhost) to (remote server) yielded the Error 27123 which, appears to be a credentials-related issue. After spending several hours the resolution appears to be one of assigning local-to-the-remote server Windows credentials that are used to launch DTEexec.exe. I am using VS2012 Ultimate locally with SQL Server 2014 Developer version and remote SQL version 2012 SP1. However, my attempts have failed so far.
I would VERY much like to be able to deploy to the remote server inside of VS2012, including creating folders, etc but am still at a loss as to the missing piece needed.
We do not have Active Directory set up as the remote is on the Amazon S3 cloud bit other than that is pretty much a plain vanilla setup. I also noted some folks suggested a Kerberos-based response but before I ask our network guru to proceed I'd like at least to get confirmation.
I AM able to manually FTP, install and run packages when remoted in but that stinks for my contractor who I would also like to be able to have me out of his way. s
All found online materials have not yet yielded the one last piece. I suspect my ignorance rather than the lack of a real solution and would appreciate any guidance.
Thanks in advance.
Box was corrupt and was cleaned up and operational. Now, SQL Server will not connect to my db. I checked services and found that mssqlserver, SQL Server agents won't start. Gives error
Cannot connect to local server
They are set to automatically start, but manually starting gives the same error.
I cleaned his box with this recipe that I use successfully on dozens of computers. All other software is running fine. His box also had a failing disk so I xxcloned (XXClone.com) his disk to a fresh new disk. I believe the cleaning is an unrelated issue, but whatever it takes to fix it we are happy to try. I know many people with this SQL Server issue, and over the years have fixed it a few ways, but I am tight on time, so I suggested he get help here.
THOROUGH BADDY CLEAN. Clean a Windows Machine without Formatting it or losing Data
STEP 1
If Ransomware or some baddy is taking over our MBR or Partition so you cannot escape it, and cannot run safe mode, the ICE Ransomware being one of many examples.....
http://www.bleepingcomputer.com/virus-removal/remove-ice-cyber-crime-center-ransomware
use a empty USB stick and HitManPro (the free version will remove)
http://www.surfright.nl/en/hitmanpro/
STEP 2
Reboot in Safe mode with networking by rebooting and holding down F8 key. None of this will permanently fix your computer unless you are in SAFE MODE w/ NETWORKING
Download RKill and run it
Download ComboFix from BleepingComputer.org and run it
Download SmitFraudFix and run it
Download AntiMalwareBytes to catch everything those did not
I can clean any machine no matter how badly infected with these tools in safe mode. Will keep recurring if attempted in Normal Mode. Safe mode is the key.