When Reporting Tools Setup is used t deploy the reports to SQL Server Reporing Services an error be produced if the default configuration of SSRS has not been amended (I thought I’d blogged about this error before, but when trying to find it to send the post to someone I couldn’t find it).
The error produced is the following:
I’ve just finished doing some maintenance on one of my development servers and encountered a problem where I could not restart the SQL Server. The development server was a virtual machine running on VMWare which had a second virtual HDD installed for SQL Server to store the database and log files. This disk had been provisioned at 200GB and over time had acquired a lot of files, such as database backups, which became unnecessary and had filled the 200GB.
I needed to get some of the space back on the VM host so I stopped the SQL Server, copied the SQL mdf and log files to a new HDD, deleted the SQL HDD and then set the drive letter of the new HDD to that of the old one.
I then tried to start SQL Server and received the following error:
A while ago I posted about a problem with a collation conflict on a couple of columns in the Tax table. It seems I posted about how to fix the problem, but it seems I didn’t post how I found the problem columns.
I did this with a fairly simple SQL script:
DECLARE @Collation SYSNAME SET @Collation = 'SQL_Latin1_General_CP1_CI_AS' SELECT TABLE_NAME AS 'Table' ,COLUMN_NAME AS 'Column' ,DATA_TYPE AS 'Data Type' ,COLLATION_NAME AS 'Collation Name' FROM INFORMATION_SCHEMA.COLUMNS WHERE DATA_TYPE IN ('varchar','char','nvarchar','nchar','text','ntext') AND COLLATION_NAME <> @Collation
This is an update of the Microsoft Dynamics GP 2010 book she wrote a few years ago, which has been updated for Microsoft Dynamics GP 2013:
In brief this book covers:
- Plan, install, and implement Microsoft Dynamics GP 2013 with real-world advice from a Microsoft Dynamics GP MVP
- Learn how to set up the core modules in Microsoft Dynamics GP effectively following detailed, step-by-step instructions
- Discover additional tools and resources available for your Dynamics GP
I’m currently involved with a couple of projects where we have needed to migrate databases from one SQL Server to another and needed to do so more than once.
Prior to the first copy, we used a script to load the users into SQL Server and then restored the databases and had no problems.
Later on, after changing some of the permissions to databases we had need to remigrate some of them over. However, we found that users could not access some databases and when we tried to add them we got the following error;
Msg 15023, Level 16, State 1, Line 1
User, group, or role 'pidev' already exists in the current database.
It was looking very like we would need to go through each database and remove access and then regrant it all; a labourious process. A quick Google found me a page from Julian Kuiters which introduced me to the ALTER USER command. The following code will run against the selected database and tie together the SQL Server user with the user in the database without any other work;
ALTER USER pidev WITH LOGIN = pidev
The first highlighted element needs to be changed to the database you want to update the user on and then the following two entries are the usernames which need to be linked (these should be set to the same value).
I was in the process of building a virtual machine to do a test upgrade of Microsoft Dynamics GP for a client when I got this error message;
I know things go wrong and I don’t mind error messages telling me that they have gone wrong; in fact, a good error with details is a good thing to see when there is a problem. But I do mind when the error message doesn’t actually tell me anything (one company I worked with produced error code 0 for every single error which everyone hated but it took about five years before the error handler got fixed to return the real error).
I did a little digging and it turned out to be a nice easy fix; when the VM was created the HDD space allocated hadn’t been big enough for the size of the databases being restored to it. I added a new (larger) virtual HDD to the VM and was able to restore the databases without further error.
I covered a wide variety of topics mainly around GP and related products as well as a few around SQL Server but I’ve not actually done a post on the “correct” installation process of installing SQL Server for use with Microsoft Dynamics GP (I highlight correct as I’m sure some people will disagree with how I am doing the installation).
With the release of Microsoft SQL Server 2012 I thought it was time to rectify this. I am going to be installing the Enterprise Edition of Microsoft SQL Server 2012 but the process is the same for each of the versions. The install is being done as I usually do them on a VM for testing/demo purposes; I would pay more attention to security and the location of the log and data folders if this were being done on a production machine.
To install SQL Server, run the setup utility on the installation media which will open the SQL Server Installation Center;
Microsoft have started the Microsoft Dynamics GP 2013 Feature of the Day series on the Inside Microsoft Dynamics GP Blog.
The thirty first feature they’ve announced is Named System Database.
In all versions of Microsoft Dynamics GP so far, the System database has been called DYNAMICS and could not be changed. This meant only a single instance (System and Company databases) of Microsoft Dynamics GP could be installed into an instance of SQL Server.
In Microsoft Dynamics GP 2013 this restriction has been removed in a new deployment. From this version onwards, the System database no longer needs to be called DYNAMICS but can be named during the installation/deployment process.
I typically like to see rollups come out as they tend to fix bugs and add new features but yesterday I advised a customer to install rollup 1 for Management Reporter.
Rollup 2 can be downloaded from here (CustomerSource or PartnerSource login required).
This one adds support for SQL Server 2012 as well as other bug fixes and enhancements to the currency translation.